--- Comment #11 from joel at gcc dot gnu dot org 2008-12-09 20:11 ---
I wondered if I had a mistake in my testing since some of the later results
didn't make sense as I thought about them. I am pretty convinced now this
is NOT a strict aliasing problem in psim.
Broken when
--- Comment #1 from joel at gcc dot gnu dot org 2008-12-03 16:54 ---
Created an attachment (id=16818)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16818action=view)
program to run with psim
This is a random ACATS test executable that can be run with psim to show if it
works or
--- Comment #2 from rguenth at gcc dot gnu dot org 2008-12-03 17:04 ---
Does it work built with -fno-strict-aliasing? -O1 or -O0?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38387
--- Comment #3 from joel at gcc dot gnu dot org 2008-12-03 17:07 ---
Created an attachment (id=16819)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16819action=view)
psim device tree
Run as follows:
powerpc-rtems4.10-run -f psim_tree a22006c
Expected output:
,.,. A22006C ACATS
--- Comment #4 from joel dot sherrill at oarcorp dot com 2008-12-03 17:09
---
Subject: Re: psim miscompiled [regression]
rguenth at gcc dot gnu dot org wrote:
--- Comment #2 from rguenth at gcc dot gnu dot org 2008-12-03 17:04
---
Does it work built with
--- Comment #5 from joel at gcc dot gnu dot org 2008-12-03 17:22 ---
Works with -O0
(CFLAGS=-O0 ~/old/test-gcc/gdb-6.8/configure --target=powerpc-rtems4.10
--enable-sim --enable-sim-hardware --enable-timebase --enable-sim-trace
--prefix=/n/12/joel/test-gcc/install/ make make install)
--- Comment #6 from joel at gcc dot gnu dot org 2008-12-03 17:32 ---
At -O1, there was a core dump.
(gdb) run -f psim_tree.joel
/home/joel/test-gcc/gcc-svn/gcc/testsuite/ada/acats/work-psim/tests/a/a22006c/a22006c
Starting program: /home/joel/test-gcc/install/bin/powerpc-rtems4.10-run
--- Comment #7 from joel at gcc dot gnu dot org 2008-12-03 17:40 ---
Works with -fno-strict-aliasing added.
Core dumps at -O1
Works at -O0.
Is there anything I can do to narrow this down further?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38387
--- Comment #8 from steven at gcc dot gnu dot org 2008-12-03 18:53 ---
You can enable the aliasing warnings (-Wstrict-aliasing=2) and see if there are
warnings when compiling psim.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38387
--- Comment #9 from joel at gcc dot gnu dot org 2008-12-03 20:33 ---
Created an attachment (id=16822)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16822action=view)
Warning log from gdb build
This is grep warning build.log | sort -u from a build with
-Wstrict-aliasing=2
--
--- Comment #10 from joel at gcc dot gnu dot org 2008-12-03 20:35 ---
I have attached e.log which contains the warnings. All of the warnings in
ppc-instructions are for taking the address of a double and casting it as
an unsigned64 *.
ld-insn.c:814 is a print so that's irrelevant.
11 matches
Mail list logo
