avr-gcc-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-gcc-list] GCC 3.0 thread


From: J Wunsch
Subject: Re: [avr-gcc-list] GCC 3.0 thread
Date: Tue Jan 16 00:22:04 2001

Denis Chertykov <address@hidden> wrote:

> Use the binutils from CVS.

Well, as i said, i'm reluctant to use too much beta software.  I'm
maintaining the avr-* FreeBSD ports, and the general policy there is
to not use beta stuff (or i would have to prepare a second port just
for the beta version, to provide people the option to fall back to
`stable' versions).

>> But what about the internal consistency compilation problems i
>> mentioned?  Have they been fixed meanwhile?
> 
> You don't point to any real bug.

Hmm, maybe.  The old compiler used

__tmp_reg__ = r0

while the new one uses

__tmp_reg__ = 0

Does that mean the current version of the assembler understands the
latter as well as the former as a valid register naming?

(Actually, there was a bug in my report, regarding the number of
parameters to REGISTER_MOVE_COST() being inconsistent between the
machine-dependent .h files and their usage in the machine-independent
..c files.  But that might have been a temporary one of that particular
version.)

>> I can't download the full > 10 GB of gcc source code each day, just in
>> order to check whether it's fixed now.
> 
> Use CVS. It's really nice.

Well, i know CVS and know it's nice:), we've been using at for FreeBSD
since 1993...  But i don't want to become a gcc developer, and it's
not all that practical for daily work (in particular not when used as
remote CVS).  I'll give it another try by using one of the snapshot
tarballs for binutils.

>> spasibo bolshoye za otviet!
> 
> koi8 for Russian.

Hmm, sorry, i don't have an environment set up for KOI8-R.  Also, your
English is certainly way better than my Russian. ;-)  Nevermind...

-- 
J"org Wunsch                                           Unix support engineer
address@hidden         http://www.interface-systems.de/~j



reply via email to

[Prev in Thread] Current Thread [Next in Thread]