https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46861
Eric Gallager changed:
What|Removed |Added
Target||alphaev5-unknown-linux-gnu
S
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46861
--- Comment #5 from Jay 2010-12-11 09:40:39 UTC
---
No problem with 4.4.5 either.
j...@alphalinux:~$ $HOME/gcc-4.4.5/bin/gcc -v
Using built-in specs.
Target: alphaev5-unknown-linux-gnu
Configured with: /home/jay/src/gcc-4.4.5/configure -prefix=/
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46861
--- Comment #4 from Jay 2010-12-11 08:47:22 UTC
---
It appears to also be ok in 4.3.5.
j...@alphalinux:~$ $HOME/gcc-4.3.5/bin/gcc -v
Using built-in specs.
Target: alphaev5-unknown-linux-gnu
Configured with: /home/jay/src/gcc-4.3.5/configure -pr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46861
--- Comment #3 from Jonathan Wakely 2010-12-09
11:43:07 UTC ---
(In reply to comment #2)
> Right, I already reported: no problem with 4.5.1.
> 4.2.4 is what Debian 5.0 has though.
Then it should be reported to Debian if they're still maintaining
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46861
--- Comment #2 from Jay 2010-12-09 11:21:35 UTC
---
Right, I already reported: no problem with 4.5.1.
4.2.4 is what Debian 5.0 has though.
I'll stick with my workaround.
I can try 4.3.x, 4.4.x if there is interest (i.e. in fixing them if they are
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46861
Richard Guenther changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|