On 02/14/16 14:34, Mark Millard wrote:
clang's code base is not familiar material for me nor do I have solid
reference material for the FreeBSD TARGET_ARCH=powerpc ABI rules so
the below has my guess work involved. The following code appears to
have hard wired a global, unvarying constant
A top post as I figured out what is going on:
My original src.conf had a bad "optimization" where I had been thinking that
since I had a working compiler that was not being updated with new source code
that I could avoid the time to rebuild it during the bootstrap:
WITHOUT_GCC_BOOTSTRAP=
But
On Sun, Feb 14, 2016 at 12:21 PM, Mark Millard wrote:
> Is buildworld supposed to use /usr/include's area for finding files by
> default? (I'm not talking of ${WORLDTMP}/usr/include but of just
> /usr/include.)
>
Yes, but only though the end of the bootstrap phase.
> It
On 2016-Feb-14, at 11:29 AM, Roman Divacky wrote:
>
> Fwiw, the code to handle the vaarg is in
> tools/clang/lib/CodeGen/TargetInfo.cpp:PPC32_SVR4_ABIInfo::EmitVAArg()
>
> You can take a look to see whats wrong.
>
> On Sat, Feb 13, 2016 at 07:03:29PM -0800, Mark Millard
Is buildworld supposed to use /usr/include's area for finding files by default?
(I'm not talking of ${WORLDTMP}/usr/include but of just /usr/include.)
It does use /usr/include's area for some contexts: self-hosted builds without a
special XCC full path (e.g., an implicit TARGET_ARCH=powerpc on
Fwiw, the code to handle the vaarg is in
tools/clang/lib/CodeGen/TargetInfo.cpp:PPC32_SVR4_ABIInfo::EmitVAArg()
You can take a look to see whats wrong.
On Sat, Feb 13, 2016 at 07:03:29PM -0800, Mark Millard wrote:
> I've isolated another clang 3.8.0 TARGET_ARCH=powerpc SEGV problem that shows