[Bug target/16120] [3.5 Regression] bootstrap failure on arm-linux

2004-08-25 Thread rearnsha at gcc dot gnu dot org
--- Additional Comments From rearnsha at gcc dot gnu dot org 2004-08-25 16:13 --- This has been fixed at some point -- at least, a recent build on ARM-linux bootstrapped ok for me. -- What|Removed |Added ---

[Bug target/16120] [3.5 Regression] bootstrap failure on arm-linux

2004-08-13 Thread random at rnd dot cx
-- What|Removed |Added CC||random at rnd dot cx http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16120 --- You are receiving this mail be

[Bug target/16120] [3.5 Regression] bootstrap failure on arm-linux

2004-08-03 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-08-03 06:11 --- Can someone attach the preprocessed source file? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16120 --- You are receiving this mail because: --- You reported the bug, or are watching the repor

[Bug target/16120] [3.5 Regression] bootstrap failure on arm-linux

2004-06-22 Thread rearnsha at gcc dot gnu dot org
--- Additional Comments From rearnsha at gcc dot gnu dot org 2004-06-22 16:19 --- A quick look at the failing code suggests that it would be the second call to get_insns in arm_finalize_pic that's the culprit here. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16120 --- You are

[Bug target/16120] [3.5 Regression] bootstrap failure on arm-linux

2004-06-22 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-06-22 16:03 --- Comfirmed, someone will have to go through the whole of arm.c with a comb to figure out which get_insns () needs to be changed to entry_of_function. -- What|Removed |Ad

[Bug target/16120] [3.5 Regression] bootstrap failure on arm-linux

2004-06-21 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-06-21 19:29 --- The fix should look like something I did for the hppa-linux fix, if I have time today I will look into this see where the bug, it is most likely in target specific code. -- What|Removed