cvs commit: src/share/mk bsd.cpu.mk

[M. Warner Losh]

In message: <20060721125118.GA6326 at dragon.NUXI.org>
            "David O'Brien" <obrien at FreeBSD.ORG> writes:
: On Thu, Jul 20, 2006 at 05:39:27PM -0600, M. Warner Losh wrote:
: > In message: <44C012D1.2050905 at cs.rice.edu>
: >             Alan Cox <alc at cs.rice.edu> writes:
: > : Warner Losh wrote:
: > : 
: > : >imp         2006-07-20 22:42:48 UTC
: > : >
: > : >  FreeBSD src repository
: > : >
: > : >  Modified files:
: > : >    share/mk             bsd.cpu.mk 
: > : >  Log:
: > : >  Remove ALPHA optimization pointer for gcc flags.
: > : >  Add ARM optimization pointer for gcc flags.
: > : >  
: > : >  Revision  Changes    Path
: > : >  1.53      +1 -1      src/share/mk/bsd.cpu.mk
: > : >  
: > : >
: > : I'm curious.  Is there an ETA for a working arm tool-chain in CVS HEAD?
: > 
: > As soon as I can work out with David how he wants me to commit it.  Or
: > until I get tired of waiting and make any mistakes I make his problem
: > as punishment for not getting back to me in a timely manner.
: 
: I'm working on getting it in upstream first - what was decided in the
: past as the proper path to grow new architectures in FreeBSD.  Otherwise
: we can go down the same path we did in the past where our toolchain
: diverged very far from the GNU sources and we were left on own
: maintaining them.  Note that from what I've seen none of the anxious ARM
: kernel developers have spent one once of time on this issue.

I'm going to call bullshit on this.

I've been trying for over six months to work with you to get these
changes into the tree and fed upstream.  I'm tired of you blowing me
off.  I am deeply offended that you accuse me of doing nothing when
I've been repeatedly approaching you over the past year trying to get
things into the tree.  I send you mail proposing things to make this
happen, and you don't get back with me about the proposals.

You've never told me that you were working to get these changes
upstream.  I'd be happy to help with this process if you'd only tell
me what to do.  Who should I send email to with the patches?  What
paperwork needs to be filled out?  What can I do to help ensure that
the changes are fed upstream.

Finally, you ignored my proposal that we import on the vendor branch
the changes we have today, understanding that when gcc 4 comes you are
under 0 obligation to do anything with them.  Since they would be on
the vendor branch, it wouldn't interfere with your gcc 4 work.  It
would allow us to MFC the changes.

: I'd like to ask when we'll get ARM resources in the FreeBSD.org cluster
: so committers can have access to ARM - I don't.  So it is hard to test
: anything.  Until a month ago no one would agree on a reference platform
: so toolchain work could be tested vs.  spending all my time trying to get
: something working that no one else had.  I am still waiting to get the
: ARM board I purchased in my hands and working.

We've tested these patches.  They work.  Why must you be so insistant
on a proceedure that makes it so hard to get things done.  There will
be times that the cluster doesn't have the resources needed, and
you'll have to take it on faith that another architecture works.

You can compile test things, and audit the code and provide feedback
based.  Yet none has been forthcoming despite my trying to draw it out
of you for at least six months now.

: Alan I'm curious, for you what is the rush?

6.2.  I've told you this before.  We want to make a big splash with
the emebedded arm stuff, and I really want to get things in before
then.

I'm extremely frustrated on this and this current situation is intolerable.

Warner