[Top][All Lists]

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

Re: [bug-mes] ARM mes on wip-arm - Runtime setup

From: Danny Milosavljevic
Subject: Re: [bug-mes] ARM mes on wip-arm - Runtime setup
Date: Mon, 11 Mar 2019 15:22:37 +0100

Hi Janneke,

On Mon, 11 Mar 2019 13:52:28 +0100
Jan Nieuwenhuizen <address@hidden> wrote:

> Danny Milosavljevic writes:
> > it will not work because build.sh overwrites it.  
> Yes.  Not sure what to do; distros like Debian set all kinds of flags
> that break things.  Prolly just best for now to hardcode this exception
> for arm?  Maybe I'll have another look at autotools if it fixes
> such things for us, or if we can steal their tricks :-)

In this case I only have the flag because I want the bootstrapping with gcc to 

(1) similar to the mescc-compiled version
(2) reduced complexity - no two different frame pointers, two different 
instruction decoders, two different branch offset calculations (!) etc

So hard-coding CFLAGS=-marm would be fine.

Maybe even hard-coding CC="gcc -marm" would work and be more paranoid.  Not 

A bootstrapper really shouldn't inherit a bunch of things from the environment, 
so CFLAGS not being overridable is fine here.

Attachment: pgpAj8CGGdyqa.pgp
Description: OpenPGP digital signature

reply via email to

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