public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: bootstrap/6225: [x86 x sh-elf] reload1.c failure
@ 2002-11-29 17:36 tm
  0 siblings, 0 replies; 3+ messages in thread
From: tm @ 2002-11-29 17:36 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

The following reply was made to PR bootstrap/6225; it has been noted by GNATS.

From: tm <tm@mail.kloo.net>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	gniibe@m17n.org, jh@suse.cz, nobody@gcc.gnu.org, tm@kloo.net,
	gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/6225: [x86 x sh-elf] reload1.c failure
Date: Wed, 20 Nov 2002 18:45:21 -0800 (PST)

 On 21 Nov 2002 bangerth@dealii.org wrote:
 
 > Old Synopsis: reload1.c failure for sh-elf.  Bootstrap failure on sh4-unknown-linux-gnu
 > New Synopsis: [x86 x sh-elf] reload1.c failure
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bangerth
 > State-Changed-When: Wed Nov 20 18:08:49 2002
 > State-Changed-Why:
 >     This is a rather old bootstrap failure. Can you please check
 >     whether this still happens with newer versions of gcc and
 >     report back to us what you find?
 >     
 >     Has the patch you mention in your report been applied in
 >     the meantime?
 >     
 >     Thanks
 >       Wolfgang
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6225
 > 
 
 I've tested the testcase against CVS head, specifically:
 
 gcc version 3.3 20021119 (experimental)
 
 and the resultant output code compiled with -O2 seems correct:
 
 .L232:
         .loc 1 288 0
         mov     #64,r6
         add     r14,r6
         mov.l   @(12,r6),r0
         mov.l   @(8,r6),r6
         sub     r6,r0
         mov     #64,r6
         add     r14,r6
         mov.l   r0,@(8,r6)    <- r14 + 64 + 8 = r14 + 72 = correct
 
 This seems ok to close.
 
 Toshi
 
 
 


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: bootstrap/6225: [x86 x sh-elf] reload1.c failure
@ 2002-11-30  4:26 bangerth
  0 siblings, 0 replies; 3+ messages in thread
From: bangerth @ 2002-11-30  4:26 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, gniibe, jh, nobody, tm

Synopsis: [x86 x sh-elf] reload1.c failure

State-Changed-From-To: feedback->closed
State-Changed-By: bangerth
State-Changed-When: Wed Nov 20 19:06:46 2002
State-Changed-Why:
    Reportedly works now.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6225


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: bootstrap/6225: [x86 x sh-elf] reload1.c failure
@ 2002-11-29 10:36 bangerth
  0 siblings, 0 replies; 3+ messages in thread
From: bangerth @ 2002-11-29 10:36 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, gniibe, jh, nobody, tm

Old Synopsis: reload1.c failure for sh-elf.  Bootstrap failure on sh4-unknown-linux-gnu
New Synopsis: [x86 x sh-elf] reload1.c failure

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Wed Nov 20 18:08:49 2002
State-Changed-Why:
    This is a rather old bootstrap failure. Can you please check
    whether this still happens with newer versions of gcc and
    report back to us what you find?
    
    Has the patch you mention in your report been applied in
    the meantime?
    
    Thanks
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6225


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-11-21  3:06 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-11-29 17:36 bootstrap/6225: [x86 x sh-elf] reload1.c failure tm
  -- strict thread matches above, loose matches on Subject: below --
2002-11-30  4:26 bangerth
2002-11-29 10:36 bangerth

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).