This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: m68k bootstrapping broken


On Tue, Jan 06, 2004 at 12:23:34PM +0100, Bernardo Innocenti wrote:
 
> btw, since you're one of the few who can test GCC 3.4 on m68k-linux,
> would you mind to review some of these PRs?  I've recently checked
> some of them to see if I could help, but (un)fortunately none of
> them affect my targets:
> 
> http://gcc.gnu.org/bugzilla/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=m68k&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED

looking through it, I can try the perl bug again but the other
bugs are either out of reach at this stage or not linux.

If I find time I will try to look at the bootstrapping problem.

> >>Hmmm... I'd suspect anything that changes m68k.md or the target
> >>hooks in m68k.h.  Perhaps linux.h overrides something that
> >>interacts with register allocation?
> >
> >Linux has different register usage for function call returns
> >but only scratch registers are involved. Other than that there
> >is nothing close to suspicious.
> 
> Then all m68k targets should be seing the same ICE, which is not
> the case.

possibly not many people with m68k targets do bootstrapping
very often nowadays - afaics only debian-m68k.

Eg the warning you have just recetnly fixed in CVS would make
every bootstrap attempt fail on all m68k plattforms, not just
linux.

Richard


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]