aboutsummaryrefslogtreecommitdiff
path: root/gcc/vr-values.c
diff options
context:
space:
mode:
authorAlexandre Oliva <oliva@adacore.com>2019-08-16 03:38:49 +0000
committerAlexandre Oliva <aoliva@gcc.gnu.org>2019-08-16 03:38:49 +0000
commit967a322edecf6d8ef8ab58ff7a50cf58c26e7de6 (patch)
treecc70600eb024f8ddd5773eb3f28903ad234557d6 /gcc/vr-values.c
parent1ce521ece9a514dd8c5a3baa6e66bab928fd5e7c (diff)
downloadgcc-967a322edecf6d8ef8ab58ff7a50cf58c26e7de6.zip
gcc-967a322edecf6d8ef8ab58ff7a50cf58c26e7de6.tar.gz
gcc-967a322edecf6d8ef8ab58ff7a50cf58c26e7de6.tar.bz2
i386/asm-4 test: use amd64's natural addressing mode on all OSs
gcc.target/i386/asm-4.c uses amd64's natural PC-relative addressing mode on a single platform, using the 32-bit absolute addressing mode elsewhere. There's no point in giving up amd64's natural addressing mode and insisting on the 32-bit one when we're targeting amd64, and having to make explicit exceptions for systems where that's found not to work for whatever reason. If we just use the best-suited way to take the address of a function behind the compiler's back on each target variant, we're less likely to hit unexpected failures. for gcc/testsuite/ChangeLog * gcc.target/i386/asm-4.c: Use amd64 natural addressing mode on all __LP64__ targets. From-SVN: r274559
Diffstat (limited to 'gcc/vr-values.c')
0 files changed, 0 insertions, 0 deletions