https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107046
--- Comment #5 from Jeffrey A. Law <jeffreyalaw at gmail dot com> --- First, let's not focus too much on that specific test. There's others: Tests that now fail, but worked before (20 tests): rx-sim: gcc.c-torture/execute/ieee/hugeval.c execution, -O1 rx-sim: gcc.c-torture/execute/ieee/hugeval.c execution, -O2 rx-sim: gcc.c-torture/execute/ieee/hugeval.c execution, -O2 -flto -fno-use-linker-plugin -flto-partition=none rx-sim: gcc.c-torture/execute/ieee/hugeval.c execution, -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects rx-sim: gcc.c-torture/execute/ieee/hugeval.c execution, -O3 -g rx-sim: gcc.c-torture/execute/ieee/hugeval.c execution, -Os rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -O1 rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -O2 rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -O2 -flto -fno-use-linker-plugin -flto-partition=none rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -O3 -g rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -Og -g rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -Os rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -O1 rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -O2 rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -O2 -flto -fno-use-linker-plugin -flto-partition=none rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -O3 -g rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -Og -g rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -Os Given the magic hackery going on inside the RX target files, I wonder if we should skip the entire ieee suite for rx.
