Re: Patches for coldfire v4e
Hi, Sorry, I missed ChangeLog patches. Regards, C Jaiprakash --- [EMAIL PROTECTED] wrote: > Hi, > Attached are the patches for coldfire v4e. These > changes are originally contributed by Peter Barada. > I > have migrated and tested these changes from gcc 3.04 > to gcc 3.4 and now to mainline. > Since coldfire v4e has MMU we need to support > m68k-linux target for coldfire v4e. To support > m68k-linux for coldfire v4e I need to modify > t-linux. > But I suppose this is not desirable. In that case we > might have to create another target, maybe > coldfire-linux. Please give your > comments/suggestions > on this. Is it ok to modify t-linux or > coldfire-linux > should be created. > > Thanks and Best Regards, > C Jaiprakash > > > > __ > Do you Yahoo!? > Yahoo! Small Business - Try our new resources site! > http://smallbusiness.yahoo.com/resources/ __ Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail ChangeLog.patch Description: ChangeLog.patch
Re: Patches for coldfire v4e
Hi, > > Attached are the patches for coldfire v4e. These > > changes are originally contributed by Peter > Barada. I > > have migrated and tested these changes from gcc > 3.04 > > to gcc 3.4 and now to mainline. > > Thank you for submitting this patch. I've not yet > had the time to perform a full review. Maybe I'll > be able to do some testing over the week-end. > > I noticed a few things: > > - In many places code is mis-indented or has >minor white-space glitches; I will recheck all the formating issues and submit the patches. > - You don't seem to consistently patch both > MOTOROLA >and !MOTOROLA paths. Is this intentional? > AFAIK, >there are no ColdFire targets using the MIT > syntax, >but we need to be consistent; I think it is only for the new patterns that these paths are not followed. Do you want me to change them as well? > - The patch isn't yet updated to the .opt > conversion >that occurred on mainline a few days ago. > Changing >it should be trivial; I will do that. > > Since coldfire v4e has MMU we need to support > > m68k-linux target for coldfire v4e. To support > > m68k-linux for coldfire v4e I need to modify > t-linux. > > But I suppose this is not desirable. In that case > we > > might have to create another target, maybe > > coldfire-linux. Please give your > comments/suggestions > > on this. Is it ok to modify t-linux or > coldfire-linux > > should be created. > > What are the changes you need to apply? > Would plain 68020 code run on v4e processor? As far > as I can see, m68k-linux isn't a multilib target. Problem occurs mainly due to restricted addressing modes in v4e. For ex v4e supports only 16-bit displacements. So all crt* files needs to be build for v4e. Also v4e does not have extended floating point instructions (XF mode) so we may have to modify t-* for fpgnulib.c. > -- > // Bernardo Innocenti - Develer S.r.l., R&D dept. > \X/ http://www.develer.com/ > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Patches for coldfire v4e
--- Daniel Jacobowitz <[EMAIL PROTECTED]> wrote: > On Thu, Apr 14, 2005 at 09:36:59AM +0200, Bernardo > Innocenti wrote: > > Daniel Jacobowitz wrote: > > > On Wed, Apr 13, 2005 at 10:10:39AM +0200, > Bernardo Innocenti wrote: > > >> > > >>So it seems adding coldfire-linux is the only > way > > >>to address this... > > > > > > Why? Adding support (if it isn't already there) > for something like > > > --with-arch=coldfire should work just as well. > > > > But how do we change behavior in > gcc/config/t-linux > > according to the switch? > > You probably don't need to. The newly built > compiler will default to > the right architecture; any assembly routines can be > keyed off an > appropriate builtin define. Will there be any issues with binutils? Assembler should also default to this architecture (coldfire). These were the additions i had to make to t-linux for coldfire LIB1ASMSRC = m68k/lb1sf68.asm LIB1ASMFUNCS = _mulsi3 _udivsi3 _divsi3 _umodsi3 _modsi3 \ _double _float _floatex \ _eqdf2 _nedf2 _gtdf2 _gedf2 _ltdf2 _ledf2 \ _eqsf2 _nesf2 _gtsf2 _gesf2 _ltsf2 _lesf2 LIB2FUNCS_EXTRA = fpgnulib.c xfgnulib.c fpgnulib.c: $(srcdir)/config/m68k/fpgnulib.c cp $(srcdir)/config/m68k/fpgnulib.c fpgnulib.c xfgnulib.c: $(srcdir)/config/m68k/fpgnulib.c echo '#define EXTFLOAT' > xfgnulib.c cat $(srcdir)/config/m68k/fpgnulib.c >> xfgnulib.c MULTILIB_OPTIONS = mcfv4e EXTRA_MULTILIB_PARTS= crtbegin.o crtend.o crtbeginS.o crtendS.o crtbeginT.o EXTRA_MULTILIB_OPTIONS=-mcfv4e LIBGCC = stmp-multilib INSTALL_LIBGCC = install-multilib Can these also be taken care of? LIB2FUNCS_EXTRA? EXTRA_MULTILIB_PARTS? etc Regards, C Jaiprakash __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/
