On 01/16/14 11:23, Dominique Dhumieres wrote:
The test gcc.c-torture/execute/pr59747.c fails on darwin13 at execution time 
(Abort)
for all tested optimizations, -m32/-m64, and gcc versions before or after the 
commit.

Should I
(1) reopen pr59749,
(2) open a new pr,
(3) let you handle the problem without further fuss?

For (1) or (2) do you need a preprocessed file?
I'm certainly not seeing 59747 failing anymore:

PASS: gcc.c-torture/execute/pr59747.c compilation,  -O0
PASS: gcc.c-torture/execute/pr59747.c execution,  -O0
PASS: gcc.c-torture/execute/pr59747.c compilation,  -O1
PASS: gcc.c-torture/execute/pr59747.c execution,  -O1
PASS: gcc.c-torture/execute/pr59747.c compilation,  -O2
PASS: gcc.c-torture/execute/pr59747.c execution,  -O2
PASS: gcc.c-torture/execute/pr59747.c compilation, -O3 -fomit-frame-pointer
PASS: gcc.c-torture/execute/pr59747.c execution,  -O3 -fomit-frame-pointer
PASS: gcc.c-torture/execute/pr59747.c compilation,  -O3 -g
PASS: gcc.c-torture/execute/pr59747.c execution,  -O3 -g
PASS: gcc.c-torture/execute/pr59747.c compilation,  -Os
PASS: gcc.c-torture/execute/pr59747.c execution,  -Os
PASS: gcc.c-torture/execute/pr59747.c compilation,  -Og -g
PASS: gcc.c-torture/execute/pr59747.c execution,  -Og -g
PASS: gcc.c-torture/execute/pr59747.c compilation, -O2 -flto -fno-use-linker-plugin -flto-partition=none PASS: gcc.c-torture/execute/pr59747.c execution, -O2 -flto -fno-use-linker-plugin -flto-partition=none PASS: gcc.c-torture/execute/pr59747.c compilation, -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects PASS: gcc.c-torture/execute/pr59747.c execution, -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects


I don't have a darwin box so I'd probably need the .i & .s files so that I could poke at it a bit with a cross compiler.

I think reopening 59749 would be appropriate.

jeff

Reply via email to