Marc Glisse writes:
> Or do you mean that it is supported, from gcc's directory, to call:
> make configure-stage1-gmp
> make all-stage1-gmp CFLAGS="something new"
Yes, that is mandated by the GCS.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756
On Sun, 20 Mar 2016, Andreas Schwab wrote:
Marc Glisse writes:
For most packages, providing CFLAGS for configure is enough, you don't
have to give them *again* to make.
The toplevel GCC Makefile needs to pass down any CFLAGS setting that has
been passed in by the user.
Yes, and passing th
Marc Glisse writes:
> For most packages, providing CFLAGS for configure is enough, you don't
> have to give them *again* to make.
The toplevel GCC Makefile needs to pass down any CFLAGS setting that has
been passed in by the user.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fing
On Sun, 20 Mar 2016, Bernd Edlinger wrote:
On 20.03.2016 11:03, Marc Glisse wrote:
On Sun, 20 Mar 2016, Bernd Edlinger wrote:
So I looked for a way to disable the asm code, and found it can be
done, but differently than for in-tree gmp. See the attached patch.
As noted in PR 67728, it seems
On 20.03.2016 11:03, Marc Glisse wrote:
> On Sun, 20 Mar 2016, Bernd Edlinger wrote:
>
>>> So I looked for a way to disable the asm code, and found it can be
>>> done, but differently than for in-tree gmp. See the attached patch.
>>>
>>> As noted in PR 67728, it seems that gcc's intrusive w
On Sun, 20 Mar 2016, Bernd Edlinger wrote:
So I looked for a way to disable the asm code, and found it can be
done, but differently than for in-tree gmp. See the attached patch.
As noted in PR 67728, it seems that gcc's intrusive way of overriding
CFLAGS also breaks GMP itself, not just MPFR,
On 19.03.2016 21:29, Marc Glisse wrote:
> On Tue, 5 Jan 2016, Richard Biener wrote:
>> On January 5, 2016 2:20:42 PM GMT+01:00, Bernd Edlinger
>> wrote:
>>> On 05.01.2016 13:58, Bernd Schmidt wrote:
On 01/05/2016 09:44 AM, Bernd Edlinger wrote:
> Using asm code is generally not desirable
On Tue, 5 Jan 2016, Richard Biener wrote:
On January 5, 2016 2:20:42 PM GMT+01:00, Bernd Edlinger
wrote:
On 05.01.2016 13:58, Bernd Schmidt wrote:
On 01/05/2016 09:44 AM, Bernd Edlinger wrote:
Using asm code is generally not desirable for in-tree mpfr builds.
Why not?
for the same reason
Hi,
On 11.01.2016 20:03, Richard Biener wrote:
> On January 11, 2016 7:21:59 PM GMT+01:00, Bernd Schmidt
> wrote:
>> On 01/05/2016 07:43 PM, Richard Biener wrote:
>>> IIRC the logic at some point at least used host CPU detection to
>>> select asm. That's undesirable if you want to run binaries
On January 11, 2016 7:21:59 PM GMT+01:00, Bernd Schmidt
wrote:
>On 01/05/2016 07:43 PM, Richard Biener wrote:
>> IIRC the logic at some point at least used host CPU detection to
>> select asm. That's undesirable if you want to run binaries on
>> different hosts. Not sure if this is still the ca
On 01/05/2016 07:43 PM, Richard Biener wrote:
IIRC the logic at some point at least used host CPU detection to
select asm. That's undesirable if you want to run binaries on
different hosts. Not sure if this is still the case with newer
gmp/mpfr, but as long as we allow the ancient ones we shoul
On 05.01.2016 20:23 Jeff Law wrote:
> On 01/05/2016 11:52 AM, Bernd Edlinger wrote:
>
>> Maybe, that can of course improve things but...
>>
>> I tried to update to gmp 6.0.0 a while ago, and I noticed that it won't
>> build unless we also update to latest mpfr and mpc at the same time.
> I just che
On 01/05/2016 11:52 AM, Bernd Edlinger wrote:
Maybe, that can of course improve things but...
I tried to update to gmp 6.0.0 a while ago, and I noticed that it won't
build unless we also update to latest mpfr and mpc at the same time.
I just checked -- mpfr-3.1.3 only requires gmp-4.1 or newer
Hi Jeff,
On 05.01.2016 19:21, Jeff Law wrote:
> On 01/05/2016 06:20 AM, Bernd Edlinger wrote:
>> Hi,
>>
>> On 05.01.2016 13:58, Bernd Schmidt wrote:
>>> On 01/05/2016 09:44 AM, Bernd Edlinger wrote:
an in-tree mpfr build enables inline asm code, which makes the
mips-bootstrap fail,
On January 5, 2016 2:20:42 PM GMT+01:00, Bernd Edlinger
wrote:
>Hi,
>
>On 05.01.2016 13:58, Bernd Schmidt wrote:
>> On 01/05/2016 09:44 AM, Bernd Edlinger wrote:
>>> an in-tree mpfr build enables inline asm code, which makes the
>>> mips-bootstrap fail,
>>> because at least mpfr 2.4.2 uses the "
On 01/05/2016 06:20 AM, Bernd Edlinger wrote:
Hi,
On 05.01.2016 13:58, Bernd Schmidt wrote:
On 01/05/2016 09:44 AM, Bernd Edlinger wrote:
an in-tree mpfr build enables inline asm code, which makes the
mips-bootstrap fail,
because at least mpfr 2.4.2 uses the "=h" constraint but in
config/mips/
Hi,
On 05.01.2016 13:58, Bernd Schmidt wrote:
> On 01/05/2016 09:44 AM, Bernd Edlinger wrote:
>> an in-tree mpfr build enables inline asm code, which makes the
>> mips-bootstrap fail,
>> because at least mpfr 2.4.2 uses the "=h" constraint but in
>> config/mips/constraints.md
>> we find: "Former
On 01/05/2016 09:44 AM, Bernd Edlinger wrote:
an in-tree mpfr build enables inline asm code, which makes the mips-bootstrap
fail,
because at least mpfr 2.4.2 uses the "=h" constraint but in
config/mips/constraints.md
we find: "Formerly the @code{hi} register. This constraint is no longer
supp
On Tue, 5 Jan 2016, Marc Glisse wrote:
On Tue, 5 Jan 2016, Bernd Edlinger wrote:
an in-tree mpfr build enables inline asm code, which makes the
mips-bootstrap fail,
because at least mpfr 2.4.2 uses the "=h" constraint but in
config/mips/constraints.md
we find: "Formerly the @code{hi} register
On Tue, 5 Jan 2016, Bernd Edlinger wrote:
an in-tree mpfr build enables inline asm code, which makes the mips-bootstrap
fail,
because at least mpfr 2.4.2 uses the "=h" constraint but in
config/mips/constraints.md
we find: "Formerly the @code{hi} register. This constraint is no longer
support
Bernd Edlinger writes:
> an in-tree mpfr build enables inline asm code, which makes the mips-bootstrap
> fail,
> because at least mpfr 2.4.2 uses the "=h" constraint but in
> config/mips/constraints.md
> we find: "Formerly the @code{hi} register. This constraint is no longer
> supported.".
>
Hi,
an in-tree mpfr build enables inline asm code, which makes the mips-bootstrap
fail,
because at least mpfr 2.4.2 uses the "=h" constraint but in
config/mips/constraints.md
we find: "Formerly the @code{hi} register. This constraint is no longer
supported.".
Using asm code is generally not
22 matches
Mail list logo