diff options
| author | Martin Liska <mliska@suse.cz> | 2022-11-25 13:05:56 +0100 |
|---|---|---|
| committer | Martin Liska <mliska@suse.cz> | 2022-12-09 10:18:56 +0100 |
| commit | d71b20fc30965ba8326ad9363d0aca9d61eb4ed3 (patch) | |
| tree | 470e936d054bb69971ad67434cd4345f5108bfa6 /gcc/fortran/st.cc | |
| parent | 3e4b8dc477c12f303171ec7f0394c97494095545 (diff) | |
| download | gcc-d71b20fc30965ba8326ad9363d0aca9d61eb4ed3.zip gcc-d71b20fc30965ba8326ad9363d0aca9d61eb4ed3.tar.gz gcc-d71b20fc30965ba8326ad9363d0aca9d61eb4ed3.tar.bz2 | |
i386: fix assert (__builtin_cpu_supports ("x86-64") >= 0)
Similar story as PR103661, we again return a negative number
for __builtin_cpu_supports:
Documentation says:
int __builtin_cpu_supports(const char *feature)
This function returns a positive integer if the run-time CPU supports feature and returns 0 otherwise.
while we return -2147483648.
Moreover, I noticed "x86-64" is not a valid option for __builtin_cpu_is,
but for __builtin_cpu_supports.
PR target/107551
gcc/ChangeLog:
* config/i386/i386-builtins.cc (fold_builtin_cpu): Use same path
as for PR103661.
* doc/extend.texi: Fix "x86-64" use.
gcc/testsuite/ChangeLog:
* gcc.target/i386/builtin_target.c: Add more checks.
Diffstat (limited to 'gcc/fortran/st.cc')
0 files changed, 0 insertions, 0 deletions