public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Peter Barada <pbarada@mail.wm.sps.mot.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/8309: [3.2/? regression][m68k] m68k-elf-gcc -m5200 produces erroneous SImode set of short varaible on stack Date: Mon, 12 May 2003 15:56:00 -0000 [thread overview] Message-ID: <20030512155601.15864.qmail@sources.redhat.com> (raw) The following reply was made to PR target/8309; it has been noted by GNATS. From: Peter Barada <pbarada@mail.wm.sps.mot.com> To: giovannibajo@libero.it, Peter.Barada@motorola.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: target/8309: [3.2/? regression][m68k] m68k-elf-gcc -m5200 produces erroneous SImode set of short varaible on stack Date: Mon, 12 May 2003 11:48:55 -0400 >you reported this bug about 6 months ago. Can you confirm whether it's >still present in 3.3 branch and mainline today? Thanks, Ok, I pulled out the prerelease of gcc-3.3 and I still see this problem: [pbarada: /tmp] > /tmp/m68k-elf-3.3/bin/m68k-elf-gcc -v Reading specs from /tmp/m68k-elf-3.3/lib/gcc-lib/m68k-elf/3.3/specs Configured with: /home/pbarada/work/cvs-wavemark/cross-linux-tools/gcc-3.3-20030508/configure --target=m68k-elf --prefix=/tmp/m68k-elf-3.3 --enable-languages=c --with-local-prefix=/tmp/m68k-elf-3.3/m68k-elf --without-headers --with-newlib --disable-shared --verbose Thread model: single gcc version 3.3 20030509 (prerelease) [pbarada: /tmp] > /tmp/m68k-elf-3.3/bin/m68k-elf-gcc -O2 -fno-common -ffixed-a2 -m5200 -S -o yy.s yy.c -dp -da yy.c.11.gcse: (insn 230 228 231 9 0x4001f420 (set (reg:SI 94) (plus:SI (subreg:SI (reg/v:HI 40) 0) (const_int 1 [0x1]))) 100 {*addsi3_5200} (nil) (nil)) (insn 231 230 232 9 0x4001f420 (set (reg/v:HI 40) (subreg:HI (reg:SI 94) 2)) 33 {*m68k.md:1024} (nil) (nil)) yy.c.23.lreg: (insn 231 230 232 10 0x4001f420 (set (subreg:SI (reg/v:HI 40) 0) (plus:SI (subreg:SI (reg/v:HI 40) 0) (const_int 1 [0x1]))) 100 {*addsi3_5200} (nil) (nil)) (insn 232 231 235 10 0x4001f420 (set (reg/f:SI 15 %sp) (plus:SI (reg/f:SI 15 %sp) (const_int 8 [0x8]))) 100 {*addsi3_5200} (nil) (nil)) yy.c.24.greg: (note 230 228 371 10 NOTE_INSN_DELETED) (insn 371 230 231 10 (nil) (set (reg:SI 1 %d1) (const_int 1 [0x1])) 30 {*m68k.md:993} (nil) (nil)) (insn 231 371 232 10 0x4001f420 (set (mem:SI (plus:SI (reg/f:SI 14 %a6) (const_int -38 [0xffffffda])) [23 rotate S4 A16]) (plus:SI (mem:SI (plus:SI (reg/f:SI 14 %a6) (const_int -38 [0xffffffda])) [23 rotate S4 A16]) (reg:SI 1 %d1))) 100 {*addsi3_5200} (nil) (nil)) Note that in yy.c.11.gcse insn 231 was (set (mem:HI...)), and in yy.c.24.greg is (set (mem:SI...))
next reply other threads:[~2003-05-12 15:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-12 15:56 Peter Barada [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-13 6:21 steven 2003-05-12 19:56 Peter Barada 2003-05-10 7:48 giovannibajo 2003-05-09 23:46 Dara Hazeghi
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030512155601.15864.qmail@sources.redhat.com \ --to=pbarada@mail.wm.sps.mot.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).