[Bug target/18592] [3.3/3.4 regression] [m68k] ICE in output_operand: invalid expression as operand

2004-12-13 Thread bernie at develer dot com
--- Additional Comments From bernie at develer dot com 2004-12-13 09:14 --- And you also need -m68020 to trigger the bug. Works fine with -m68000, so the bug must hide in one of the TARGET_68020 patterns. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18592 --- You are

[Bug target/18592] [3.3/3.4 regression] [m68k] ICE in output_operand: invalid expression as operand

2004-12-13 Thread bernie at develer dot com
--- Additional Comments From bernie at develer dot com 2004-12-13 09:29 --- It happens both on ColdFire and 680x0 (x=2), but not on 68000. output_addr_const() gets passed a TRUNCATE (HImode) rtx. I could find it in the last dump before the ICE: (insn 87 45 127 3 (set (reg:HI 0 %d0

the procurator ofJudea would

2004-12-13 Thread Malinda Vigil
Think getting a 1.95% ra . t e is impossible? Think AGAIN! We can offer you the absolute rock-bottom lowe s t ra t e,g u a ranteed. We work with all c r edit types. Visit our site now http://www.theseto.com/ Malinda Vigil of elves. for univac via indefatigable, proscription

[Bug target/18592] [3.3/3.4 regression] [m68k] ICE in output_operand: invalid expression as operand

2004-12-13 Thread bernie at develer dot com
--- Additional Comments From bernie at develer dot com 2004-12-13 09:44 --- *** Bug 18542 has been marked as a duplicate of this bug. *** -- What|Removed |Added

[Bug target/18592] [3.3/3.4 regression] [m68k] ICE in output_operand: invalid expression as operand

2004-12-13 Thread bernie at develer dot com
--- Additional Comments From bernie at develer dot com 2004-12-13 09:45 --- Please see additional comments attached to PR18542: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18542 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18592 --- You are receiving this mail because:

[Bug target/18592] [3.3/3.4 regression] [m68k] ICE in output_operand: invalid expression as operand

2004-12-13 Thread corsepiu at gcc dot gnu dot org
--- Additional Comments From corsepiu at gcc dot gnu dot org 2004-12-13 10:19 --- (In reply to comment #4) And you also need -m68020 to trigger the bug. Works fine with -m68000, so the bug must hide in one of the TARGET_68020 patterns. Note: PR 18542 also covers avr-* targets.

[Bug target/18592] [3.3/3.4 regression] [m68k] ICE in output_operand: invalid expression as operand

2004-12-13 Thread schwab at suse dot de
--- Additional Comments From schwab at suse dot de 2004-12-13 10:38 --- I.e. though this PR and PR18542 might be the same for the m68k, I doubt this bug to be identical to the ICE on the avr. You can easily check that by testing if reverting the patch from comment #2 helps.

Re: status of libunwind patches for ia64

2004-12-13 Thread David Mosberger
Hi Matthias, On Sun, 12 Dec 2004 17:55:57 +0100, Matthias Klose [EMAIL PROTECTED] said: Matthias with the patch attached and an updated gcc-3.3 package, Matthias libunwind support for ia64 seems to work for me. I Matthias couldn't install any of the built packages. I'd like to

Re: status of libunwind patches for ia64

2004-12-13 Thread Matthias Klose
David Mosberger writes: I wanted to try this but found that the gcc-3.3 has a libgcc1 package for hppa only. Is this intentional? I thought a new libgcc1 package for ia64 was needed so we pick up the libunwind built from the libunwind sources. please get the libgcc1 package from the

Re: status of libunwind patches for ia64

2004-12-13 Thread David Mosberger
On Mon, 13 Dec 2004 20:47:41 +0100, Matthias Klose [EMAIL PROTECTED] said: Matthias please get the libgcc1 package from the unstable Matthias distribution. I think I've got that one already (libgcc1 v3.4.3-2). Matthias It's currently built by the gcc-3.4 sources and includes Matthias

[Bug tree-optimization/18694] [4.0 regression] loop miscompilation at -O1 (-ftree-ch)

2004-12-13 Thread law at redhat dot com
--- Additional Comments From law at redhat dot com 2004-12-13 20:36 --- Should be fixed with today's checkin to tree-ssa-dom.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18694 --- You are receiving this mail because: --- You are on the CC list for the bug, or are

[Bug tree-optimization/18694] [4.0 regression] loop miscompilation at -O1 (-ftree-ch)

2004-12-13 Thread law at redhat dot com
-- What|Removed |Added BugsThisDependsOn|18241 | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18694 --- You are receiving this mail because: --- You

[Bug tree-optimization/18694] [4.0 regression] loop miscompilation at -O1 (-ftree-ch)

2004-12-13 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-13 21:01 --- Fixed. -- What|Removed |Added Status|ASSIGNED|RESOLVED

Bug#173513: [Bug tree-optimization/9079] [tree-ssa] Inline constant function pointers

2004-12-13 Thread sxanth at ceid dot upatras dot gr
--- Additional Comments From sxanth at ceid dot upatras dot gr 2004-12-13 22:25 --- This is present in 3.4 too static inline int foo () { return 100; } typedef int (*fptr)(); static const fptr a [] = { foo }; static inline int

Bug#256668: Another data point for this bug 256668

2004-12-13 Thread Reid Priedhorsky
Dear friendly Debian GCC folks, I believe I've encountered this bug as well. Here's the scenario: I'm starting to work on a package (homework, so I'm starting with half a dozen source files alreay), tinkering away, happily compiling, when suddenly: In file included from