[Bug c/7871] ICE on legal code, global register variables problems

[Bug c/7871] ICE on legal code, global register variables problems

[pinskia at gcc dot gnu dot org]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871



------- Additional Comments From pinskia at gcc dot gnu dot org  2003-08-20 04:17 -------
I think this is related to bug 11413 and bug 10684.

[Bug target/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[bangerth at dealii dot org]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871


bangerth at dealii dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|ICE on legal code, global   |[3.3/3.4 regression] ICE on
                   |register variables problems |legal code, global register
                   |                            |variables problems
   Target Milestone|---                         |3.4


------- Additional Comments From bangerth at dealii dot org  2003-08-29 18:04 -------
This has incorrectly not been marked as a regression. Done hereby. 
W.

[Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-01-11 00:45 -------
Two things, global registers are just evil and a bug that effects m68k should not be 
considered branching blocking.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |minor
          Component|target                      |optimization
   Target Milestone|3.4.0                       |3.4.1


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[rz at linux-m68k dot org]

------- Additional Comments From rz at linux-m68k dot org  2004-01-11 11:54 -------
Subject: Re:  [3.3/3.4 regression] ICE on legal code, global register variables problems

On Sun, Jan 11, 2004 at 12:45:53AM -0000, pinskia at gcc dot gnu dot org wrote:
> 
> ------- Additional Comments From pinskia at gcc dot gnu dot org  2004-01-11 00:45 -------
> Two things, global registers are just evil and a bug that effects m68k should not be 
> considered branching blocking.

I might be wrong, but all evidence suggests this bug affects ALL
architectures, not just m68k

It appears global regs are now completely defunct since 3.1 so the
feature could be safely removed in the next release. Not that I would
wish that, it is one of the few features that gives gcc an advantage
over competition in fields like virtual machines.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[ebotcazou at gcc dot gnu dot org]

------- Additional Comments From ebotcazou at gcc dot gnu dot org  2004-01-11 13:09 -------
Yes, the global register variable extension is broken in GCC 3.x (possibly not
in GCC 3.0.x, but those releases were barely usable anyway).

Jim, you could perhaps bring the issue to the SC so that we have a definitive
position: either it is still supported and it must be given top priority for 3.4
or it is removed.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[simonmar at microsoft dot com]

------- Additional Comments From simonmar at microsoft dot com  2004-01-11 16:38 -------
Subject: RE:  [3.3/3.4 regression] ICE on legal code, global register variables problems

> ------- Additional Comments From rz at linux-m68k dot org  2004-01-11
11:54 -------
> Subject: Re:  [3.3/3.4 regression] ICE on legal code, global register
variables problems
> 
> On Sun, Jan 11, 2004 at 12:45:53AM -0000, pinskia at gcc dot gnu dot
org wrote:
> >
> > ------- Additional Comments From pinskia at gcc dot gnu dot org
2004-01-11 00:45 -------
> > Two things, global registers are just evil and a bug that effects
m68k should not be
> > considered branching blocking.
> 
> I might be wrong, but all evidence suggests this bug affects ALL
> architectures, not just m68k
> 
> It appears global regs are now completely defunct since 3.1 so the
> feature could be safely removed in the next release. Not that I would
> wish that, it is one of the few features that gives gcc an advantage
> over competition in fields like virtual machines.

A plea for keeping the global register variable feature: our Haskell
compiler GHC (http://www.haskell.org/ghc/) absolutely relies on this.
We have thousands of users who would be affected.  Currently we are
still afloat on x86 (the bug doesn't appear to affect this architecture
yet), but for other architectures we are already having to tell people
to install GCC 2.95 in order to use GHC.  Our amd64 port is held up
because of this bug.

I'm sure we're not the only compiler that uses GCC as a backend and
relies on the register variable feature.

I've been eagerly anticipating GCC 3.4 so we can get back on track.
Please don't push this back to 3.4.1, or worse, remove support for
global registers altogether!



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[rz at linux-m68k dot org]

------- Additional Comments From rz at linux-m68k dot org  2004-01-11 17:54 -------
Subject: Re:  [3.3/3.4 regression] ICE on legal code, global register variables problems


would be pitty to remove it considering that there are some patches
so I tried the patches again.

Surprise, my original patch now works even better than it used to
work with 3.1/3.2.
Namely it does now work correctly with R. Henderson's little testcase
- I am wondering if it is just lucky coincidence?

Jim's patch also works with Richard Henderson's testcase, however it
completely breaks my test app - much worse than it did in 3.2 It appears
that this approach looses some important dependency information and
assembler instructions get reordered where they should not.

Admitedly my patch is rather hackish, but it works perfectly with
my app that does really heavilly stress global register variables.

Here is my patch again:

--- gcc-3.4-20031210/gcc/flow.c.rz      2003-12-09 04:34:06.000000000 +0100
+++ gcc-3.4-20031210/gcc/flow.c 2003-12-25 20:16:12.000000000 +0100
@@ -1797,7 +1797,10 @@
             so they are made live.  */
          for (i = 0; i < FIRST_PSEUDO_REGISTER; i++)
            if (global_regs[i])
-             mark_used_reg (pbi, regno_reg_rtx[i], cond, insn);
+             {
+               SET_REGNO_REG_SET (pbi->reg_live, i);
+               mark_used_reg (pbi, regno_reg_rtx[i], cond, insn);
+             }
        }
     }


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[rz at linux-m68k dot org]

------- Additional Comments From rz at linux-m68k dot org  2004-01-11 17:58 -------
Subject: Re:  [3.3/3.4 regression] ICE on legal code, global register variables problems

On Sun, Jan 11, 2004 at 04:39:02PM -0000, simonmar at microsoft dot com wrote:

> A plea for keeping the global register variable feature: our Haskell
> compiler GHC (http://www.haskell.org/ghc/) absolutely relies on this.

could you please test the patch I just sent out on a few architectures?



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[rth at redhat dot com]

------- Additional Comments From rth at redhat dot com  2004-01-11 20:10 -------
Subject: Re:  [3.3/3.4 regression] ICE on legal code, global register variables problems

The feature cannot be removed.  It is used heavily in both glibc
and the linux kernel.  Fortunately, in both cases it tends to be
used read-only and thus doesn't tend to trigger the bug seen here.


r~


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[simonmar at microsoft dot com]

------- Additional Comments From simonmar at microsoft dot com  2004-01-12 09:54 -------
Subject: RE:  [3.3/3.4 regression] ICE on legal code, global register variables problems

 
> ------- Additional Comments From rz at linux-m68k dot org  
> 2004-01-11 17:58 -------
> Subject: Re:  [3.3/3.4 regression] ICE on legal code, global 
> register variables problems
> 
> On Sun, Jan 11, 2004 at 04:39:02PM -0000, simonmar at 
> microsoft dot com wrote:
> 
> > A plea for keeping the global register variable feature: our Haskell
> > compiler GHC (http://www.haskell.org/ghc/) absolutely 
> relies on this.
> 
> could you please test the patch I just sent out on a few 
> architectures?

Sure.  It might take a while...

Cheers,
	Simon


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[steven at gcc dot gnu dot org]

------- Additional Comments From steven at gcc dot gnu dot org  2004-01-12 23:39 -------
Move back the target for all regressions from 3.4.1 to 3.4.0, as required by 
our bug management policy. 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|3.4.1                       |3.4.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[simonmar at microsoft dot com]

------- Additional Comments From simonmar at microsoft dot com  2004-01-14 17:45 -------
Subject: RE:  [3.3/3.4 regression] ICE on legal code, global register variables problems

 
> ------- Additional Comments From rz at linux-m68k dot org  
> 2004-01-11 17:58 -------
> Subject: Re:  [3.3/3.4 regression] ICE on legal code, global 
> register variables problems
> 
> could you please test the patch I just sent out on a few 
> architectures?

Tried it on Sparc.  Interestingly, it seems to fix the original testcase
I submitted in bug 11252,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11252.  But my app still
crashes.  I'll follow up when I have more info.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-01-14 17:49 -------
Related to bug 10684 (they really might be both caused by the same patch).

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[ebotcazou at gcc dot gnu dot org]

------- Additional Comments From ebotcazou at gcc dot gnu dot org  2004-02-03 07:46 -------
*** Bug 10684 has been marked as a duplicate of this bug. ***

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |joerg-cyril dot hoehle at t-
                   |                            |systems dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[ian at wasabisystems dot com]

------- Additional Comments From ian at wasabisystems dot com  2004-02-12 16:34 -------
There is a possible patch here:
http://gcc.gnu.org/ml/gcc-patches/2004-02/msg00119.html

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |patch


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[rz at linux-m68k dot org]

------- Additional Comments From rz at linux-m68k dot org  2004-02-13 11:41 -------
Subject: Re:  [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems


> There is a possible patch here:
> http://gcc.gnu.org/ml/gcc-patches/2004-02/msg00119.html

good work, my testapp runs with this patch. Generated
code is exactly identical to what my patch produces so
I am pretty sure this is fixed.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[simonmar at microsoft dot com]

------- Additional Comments From simonmar at microsoft dot com  2004-02-13 12:24 -------
Subject: RE:  [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

 
> ------- Additional Comments From ian at wasabisystems dot com 
>  2004-02-12 16:34 -------
> There is a possible patch here:
> http://gcc.gnu.org/ml/gcc-patches/2004-02/msg00119.html

I'm testing this patch now.

Simon


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[giovannibajo at libero dot it]

------- Additional Comments From giovannibajo at libero dot it  2004-02-16 03:15 -------
Ulrich, would you mind testing Eric's patch (http://gcc.gnu.org/ml/gcc-
patches/2004-02/msg00119.html) with the S390 testcase attacched to this bug? It 
would be great if you could confirm that it fixes it.

RZ, would you please attacch your m68k testcase as a file attacchment to this 
bug? The UUENCODE in the comment is very unhandy to extract.

Thanks
Giovanni

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |uweigand at de dot ibm dot
                   |                            |com, giovannibajo at libero
                   |                            |dot it


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[uweigand at gcc dot gnu dot org]

------- Additional Comments From uweigand at gcc dot gnu dot org  2004-02-16 14:32 -------
With GCC 3.3 on s390-ibm-linux, Eric's patch fixes the ICE.
With 3.4 and head, I do not get an ICE even without the patch ...


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[giovannibajo at libero dot it]

------- Additional Comments From giovannibajo at libero dot it  2004-02-17 10:20 -------
Simon, how did your testing session with the new patch by Eric go? Does 
everything look fine now?

Jim W., would you kindly provide your comment on the patch? You seem to 
understand very well the problem, so if you could review it it would be great, 
this feature has been broken for too much time. The patch is reported to fix 
the problem on 4 different platforms (all the testcases we have).

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[simonmar at microsoft dot com]

------- Additional Comments From simonmar at microsoft dot com  2004-02-17 10:24 -------
Subject: RE:  [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

 
> ------- Additional Comments From giovannibajo at libero dot 
> it  2004-02-17 10:20 -------
> Simon, how did your testing session with the new patch by 
> Eric go? Does everything look fine now?

I'm still trying to get it built.  The Sparc I have access to
(SourceForge compile farm) is extremely slow :-(


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[simonmar at microsoft dot com]

------- Additional Comments From simonmar at microsoft dot com  2004-02-17 16:00 -------
Subject: RE:  [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

> > ------- Additional Comments From giovannibajo at libero dot 
> > it  2004-02-17 10:20 -------
> > Simon, how did your testing session with the new patch by 
> > Eric go? Does everything look fine now?
> 
> I'm still trying to get it built.  The Sparc I have access to
> (SourceForge compile farm) is extremely slow :-(

My app still crashes.  This machine doesn't have gdb installed (or even
Emacs!) so I'm going to try to get access to another machine on which to
track down the problem further.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[simonmar at microsoft dot com]

------- Additional Comments From simonmar at microsoft dot com  2004-02-17 17:03 -------
Subject: RE:  [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

I take it back; the test app now seems to be working.  Turns out that I
had some cases of:

  test1.hc:14: warning: function called through a non-compatible type

which turn into traps in recent versions of gcc.  Changing the type of a
cast fixed it.  (suggestion: mention in the warning message that the
call has been replaced by a trap.)

I'll do some thorough tests, but on the face of it it looks like the bug
can be closed.  Great going guys!


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[giovannibajo at libero dot it]

------- Additional Comments From giovannibajo at libero dot it  2004-02-17 17:41 -------
Subject: Re:  [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

simonmar at microsoft dot com wrote:

> I take it back; the test app now seems to be working.

Pheeeeew :)

> Turns out that I had some cases of:
>
>   test1.hc:14: warning: function called through a non-compatible type
>
> which turn into traps in recent versions of gcc.  Changing the type
> of a cast fixed it.  (suggestion: mention in the warning message that the
> call has been replaced by a trap.)

Would you please file a new bugreport for this issue? If you could provide also
a minimized snippet showing this it would be great.

> I'll do some thorough tests, but on the face of it it looks like the
> bug can be closed.

The patch still needs to be reviewed and approved though. Anyway, it's now
reported to fix *all* the known testcase of this bug on different
architectures.

Thank you for your testing.
Giovanni Bajo




-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[ebotcazou at gcc dot gnu dot org]

------- Additional Comments From ebotcazou at gcc dot gnu dot org  2004-02-17 18:07 -------
> Would you please file a new bugreport for this issue? If you could provide
> also a minimized snippet showing this it would be great.

And assign it to me, since I introduced the new behaviour.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[wilson at gcc dot gnu dot org]

------- Additional Comments From wilson at gcc dot gnu dot org  2004-02-18 08:49 -------
The patch that Eric Botcazou is proposing is identical to one of the early
patches I tried.  See comment #9.  Unfortunately, I neglected to include the
patch in this bug report, which obscured it.  The patch did not work for me when
I tried it.  Indeed, if I apply Eric's patch to gcc-3.3.x, it does not work.

It works in current sources apparently by accident.  See the Oct 10 combine.c
distribute_links patch from Richard Kenner.
    http://gcc.gnu.org/ml/gcc-patches/2003-10/msg00820.html
Note that he added a reg_set_p call, and note that reg_set_p assumes that a call
clobbers all hard registers, which is technically not correct.  This wrong
assumption is documented with a ??? comment.

I do think Eric's patch is a good one.  However, if we go this route, then we
have a latent problem with LOG_LINKS that may reappear in the future.  We should
be concerned about this.  I discuss this issue in comment #9 a little bit.  We
need to make sure that LOG_LINKS involving global_regs are treated specially. 
Currently, they are treated correctly by accident.

Adding some comments to distribute_notes and reg_set_p to document this would be
a start.  Perhaps that is all we can do for now.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[giovannibajo at libero dot it]

------- Additional Comments From giovannibajo at libero dot it  2004-02-18 09:06 -------
> Indeed, if I apply Eric's patch to gcc-3.3.x, it does not work.

Just for the sake of completeness, on which platform did you see this 
behaviour? FWIW, Ulrich reported that it fixes the s390 regression on 3.3.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[wilson at specifixinc dot com]

------- Additional Comments From wilson at specifixinc dot com  2004-02-18 09:13 -------
Subject: Re:  [3.3/3.4/3.5 regression] ICE on legal
	code, global register variables problems

On Wed, 2004-02-18 at 01:06, giovannibajo at libero dot it wrote:
> Just for the sake of completeness, on which platform did you see this 
> behaviour? FWIW, Ulrich reported that it fixes the s390 regression on 3.3.

This is using the testcase Richard Henderson posted in comment #4, which
is for the m68k.  The problem is target independent, but it requires a
specific set of events which may be uncommon: set a global reg, call a
function, set the global reg again using the previous value (set by the
call).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[ian at wasabisystems dot com]

------- Additional Comments From ian at wasabisystems dot com  2004-02-27 09:21 -------
Additional patch here:
    http://gcc.gnu.org/ml/gcc-patches/2004-02/msg02590.html


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[rz at linux-m68k dot org]

------- Additional Comments From rz at linux-m68k dot org  2004-02-27 13:18 -------
Subject: Re:  [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

On Fri, Feb 27, 2004 at 09:21:17AM -0000, ian at wasabisystems dot com wrote:
> 
> ------- Additional Comments From ian at wasabisystems dot com  2004-02-27 09:21 -------
> Additional patch here:
>     http://gcc.gnu.org/ml/gcc-patches/2004-02/msg02590.html

appears to work perfectly here.

Richard


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems

[cvs-commit at gcc dot gnu dot org]

------- Additional Comments From cvs-commit at gcc dot gnu dot org  2004-02-28 02:43 -------
Subject: Bug 7871

CVSROOT:	/cvs/gcc
Module name:	gcc
Changes by:	ian@gcc.gnu.org	2004-02-28 02:43:42

Modified files:
	gcc            : ChangeLog flow.c 

Log message:
	PR optimization/7871
	* flow.c (mark_set_1): Don't add LOG_LINKS for global registers
	from or to call insns.
	(propagate_one_insn): Interpret calls as setting global registers,
	not merely clobbering them.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.2953&r2=2.2954
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/flow.c.diff?cvsroot=gcc&r1=1.581&r2=1.582



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[ian at wasabisystems dot com]

------- Additional Comments From ian at wasabisystems dot com  2004-02-28 02:45 -------
Fixed on mainline--no longer a 3.5 regression.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[3.3/3.4/3.5 regression] ICE|[3.3/3.4 regression] ICE on
                   |on legal code, global       |legal code, global register
                   |register variables problems |variables problems


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3/3.4 regression] ICE on legal code, global register variables problems

[cvs-commit at gcc dot gnu dot org]

------- Additional Comments From cvs-commit at gcc dot gnu dot org  2004-02-28 03:39 -------
Subject: Bug 7871

CVSROOT:	/cvs/gcc
Module name:	gcc
Branch: 	gcc-3_4-branch
Changes by:	ian@gcc.gnu.org	2004-02-28 03:39:24

Modified files:
	gcc            : ChangeLog flow.c 

Log message:
	PR optimization/7871
	* flow.c (mark_set_1): Don't add LOG_LINKS for global registers
	from or to call insns.
	(propagate_one_insn): Interpret calls as setting global registers,
	not merely clobbering them.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=2.2326.2.264&r2=2.2326.2.265
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/flow.c.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.572.4.1&r2=1.572.4.2



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3 regression] ICE on legal code, global register variables problems

[ian at wasabisystems dot com]

------- Additional Comments From ian at wasabisystems dot com  2004-02-28 03:40 -------
No longer a 3.4 regression.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[3.3/3.4 regression] ICE on |[3.3 regression] ICE on
                   |legal code, global register |legal code, global register
                   |variables problems          |variables problems


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3 regression] ICE on legal code, global register variables problems

[cvs-commit at gcc dot gnu dot org]

------- Additional Comments From cvs-commit at gcc dot gnu dot org  2004-02-28 13:36 -------
Subject: Bug 7871

CVSROOT:	/cvs/gcc
Module name:	gcc
Branch: 	gcc-3_3-branch
Changes by:	ian@gcc.gnu.org	2004-02-28 13:36:29

Modified files:
	gcc            : ChangeLog flow.c 

Log message:
	PR optimization/7871
	* flow.c (mark_set_1): Don't add LOG_LINKS for global registers
	from or to call insns.
	(propagate_one_insn): Interpret calls as setting global	registers,
	not merely clobbering them.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.16114.2.908&r2=1.16114.2.909
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/flow.c.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.541.2.4&r2=1.541.2.5



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3 regression] ICE on legal code, global register variables problems

[ian at wasabisystems dot com]

------- Additional Comments From ian at wasabisystems dot com  2004-02-28 13:38 -------
This bug is now fixed for 3.3.4, 3.4.0, and on mainline.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|3.4.0                       |3.3.4


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3 regression] ICE on legal code, global register variables problems

[cvs-commit at gcc dot gnu dot org]

------- Additional Comments From cvs-commit at gcc dot gnu dot org  2004-03-08 10:17 -------
Subject: Bug 7871

CVSROOT:	/cvs/gcc
Module name:	gcc
Branch: 	hammer-3_3-branch
Changes by:	matz@gcc.gnu.org	2004-03-08 10:17:40

Modified files:
	gcc            : ChangeLog.hammer flow.c reload.c 

Log message:
	2004-03-05  Ian Lance Taylor  <ian@wasabisystems.com>
	
	PR inline-asm/6162
	* reload.c (find_reloads): Only support one pair of commutative
	operands.
	
	2004-02-27  Ian Lance Taylor  <ian@wasabisystems.com>
	
	PR optimization/7871
	* flow.c (mark_set_1): Don't add LOG_LINKS for global registers
	from or to call insns.
	
	2004-02-27  Eric Botcazou  <ebotcazou@libertysurf.fr>
	
	PR optimization/7871
	* flow.c (propagate_one_insn): Interpret calls as setting global
	registers, not merely clobbering them.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.hammer.diff?cvsroot=gcc&only_with_tag=hammer-3_3-branch&r1=1.1.2.368&r2=1.1.2.369
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/flow.c.diff?cvsroot=gcc&only_with_tag=hammer-3_3-branch&r1=1.540.2.9&r2=1.540.2.10
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/reload.c.diff?cvsroot=gcc&only_with_tag=hammer-3_3-branch&r1=1.197.2.13&r2=1.197.2.14



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3 regression] ICE on legal code, global register variables problems

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-04-13 11:14 -------
*** Bug 14938 has been marked as a duplicate of this bug. ***

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bruno at clisp dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871

[Bug optimization/7871] [3.3 regression] ICE on legal code, global register variables problems

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-04-13 11:17 -------
*** Bug 14937 has been marked as a duplicate of this bug. ***

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871