On Mon, Apr 16, 2012 at 1:34 PM, Doug Hunley <doug.hunley@gmail.com> wrote:
> On Mon, Apr 16, 2012 at 13:20, Michael Mol <mikemol@gmail.com> wrote:
>> Are you using ccache?
>
> nope. no ccache, no distcc
What are you using for CFLAGS?
--
:wq
04-16-2012, 05:53 PM
Doug Hunley
dev-libs/ppl-0.12 breaks gcc?
On Mon, Apr 16, 2012 at 13:39, Michael Mol <mikemol@gmail.com> wrote:
> On Mon, Apr 16, 2012 at 1:34 PM, Doug Hunley <doug.hunley@gmail.com> wrote:
>> On Mon, Apr 16, 2012 at 13:20, Michael Mol <mikemol@gmail.com> wrote:
>>> Are you using ccache?
>>
>> nope. no ccache, no distcc
>
> What are you using for CFLAGS?
On Mon, Apr 16, 2012 at 1:53 PM, Doug Hunley <doug.hunley@gmail.com> wrote:
> On Mon, Apr 16, 2012 at 13:39, Michael Mol <mikemol@gmail.com> wrote:
>> On Mon, Apr 16, 2012 at 1:34 PM, Doug Hunley <doug.hunley@gmail.com> wrote:
>>> On Mon, Apr 16, 2012 at 13:20, Michael Mol <mikemol@gmail.com> wrote:
>>>> Are you using ccache?
>>>
>>> nope. no ccache, no distcc
>>
>> What are you using for CFLAGS?
>
> ~ $ more /etc/make.conf
> # ---[Compiler Settings]---
> CHOST="x86_64-pc-linux-gnu"
> CFLAGS="-O2 -pipe -march=native -mtune=native -mpopcnt -msahf
> -fomit-frame-pointer -fforce-addr -floop-interchange -floop-strip-mine
> -floop-block -ftree-loop-distribution -ftree-loop-linear"
-O2, -pipe, -march and -mtune look fine (though -mtune is implied by
-march), as does -mpopcnt and -msahf. -fomit-frame-pointer is implied
by -O2.
> I'm currently running ~amd64 and when I ran a world update,
> dev-libs/ppl-0.12 was pulled down, compiled and installed. At that
> point, gcc stops compiling. It doesn't matter what I try to compile,
> whether it's the dev-libs/cloog-ppl rebuild that dev-libs/ppl-0.12.
> says to do, a recompile of gcc, or anything else. They all die with
> with 'internal compiler error'. I end up having to 'emerge -k gcc' and
> then masking dev-libs/ppl-0.12 to get back to a working compiler
> chain.
Strange, isn't it. How can those bugs make it into the tree? It's ~arch,
but this should not mean that it hasn't been tested at all.
> Am I the only one facing this?
Nope.
> How did you guys get through the mud here?
Looking for ppl on bugs.gentoo org, finding bug #412117[*], rebuilding
ppl and cloog-ppl without -floop* CFLAGS, then again with floop* CFLAGS.
On 04/16/2012 10:14 AM, Doug Hunley wrote:
> I'm currently running ~amd64 and when I ran a world update,
> dev-libs/ppl-0.12 was pulled down, compiled and installed. At that
> point, gcc stops compiling. It doesn't matter what I try to compile,
> whether it's the dev-libs/cloog-ppl rebuild that dev-libs/ppl-0.12.
> says to do, a recompile of gcc, or anything else. They all die with
> with 'internal compiler error'. I end up having to 'emerge -k gcc' and
> then masking dev-libs/ppl-0.12 to get back to a working compiler
> chain.
I can't explain why the "internal compiler error" but I'd guess it's
probably something in your CFLAGS, as the other replies suggested.
But be aware that once you finally get ppl upgraded you'll need to
rebuild cloog-ppl *without* the -floop-* flags because gcc will not
build anything *with* those flags because the old cloog-ppl will
now be broken. Until you rebuild it, of course.
04-16-2012, 08:00 PM
Doug Hunley
dev-libs/ppl-0.12 breaks gcc?
On Mon, Apr 16, 2012 at 14:47, Alex Schuster <wonko@wonkology.org> wrote:
> Looking for ppl on bugs.gentoo org, finding bug #412117[*], rebuilding
> ppl and cloog-ppl without -floop* CFLAGS, then again with floop* CFLAGS.
On Mon, Apr 16, 2012 at 16:00, Doug Hunley <doug.hunley@gmail.com> wrote:
> On Mon, Apr 16, 2012 at 14:47, Alex Schuster <wonko@wonkology.org> wrote:
>> Looking for ppl on bugs.gentoo org, finding bug #412117[*], rebuilding
>> ppl and cloog-ppl without -floop* CFLAGS, then again with floop* CFLAGS.
>
> damn, I searched, didn't see this. thanks
didn't see it cause I looked on Sat, it was filed yesterday
dev-libs/ppl-0.12 breaks gcc?
