The github-repo https://github.com/LowLevelMahn/build_clfs_tools
contains the scripts, files AND complete build-logs (so no need to run
the script yourself)
separated for each step that i will use here as a "walkable" reference.
Its better read/clickable then this long email.
I'll try to keep t
The github-repo https://github.com/LowLevelMahn/build_clfs_tools
contains the scripts, files AND complete build-logs (so no need to run
the script yourself)
separated for each step that i will use here as a "walkable" reference.
The Repo Readme.MD better read/clickable then this long email. I'll
Hi Andreas!
On Fri, 02 Oct 2015 13:58:55 +0200, Andreas Schwab
wrote:
> LAST_UPDATED: Fri Oct 2 02:31:25 UTC 2015 (revision 228367)
>
> Native configuration is aarch64-suse-linux-gnu
> === libgomp tests ===
>
>
> Running target unix
> FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++
Thomas Schwinge writes:
> Hi Andreas!
>
> On Fri, 02 Oct 2015 13:58:55 +0200, Andreas Schwab
> wrote:
>> LAST_UPDATED: Fri Oct 2 02:31:25 UTC 2015 (revision 228367)
>>
>> Native configuration is aarch64-suse-linux-gnu
>
>> === libgomp tests ===
>>
>>
>> Running target unix
>> F
Hi Andreas!
On Tue, 06 Oct 2015 12:53:03 +0200, Andreas Schwab
wrote:
> Thomas Schwinge writes:
> > On Fri, 02 Oct 2015 13:58:55 +0200, Andreas Schwab
> > wrote:
> >> LAST_UPDATED: Fri Oct 2 02:31:25 UTC 2015 (revision 228367)
> >>
> >> Native configuration is aarch64-suse-linux-gnu
> >
> >
Thomas Schwinge writes:
> | The two regressed test cases use __builtin_printf instead of fprintf to
> | stderr, but as far as I know, abort is to flush all open streams before
> | process termination?
It can't, since abort must be async-signal-safe.
Andreas.
--
Andreas Schwab, sch...@linux-m6
All,
One of my colleagues on the Fortran Standardization Committee asked me
the following question:
"People are still not too familiar with the new GCC numbering scheme.
My impression is that 5.2 is just a maintenance update of 5.1. However,
they still want assurance that there are no call
On 6 October 2015 at 20:32, Toon Moene wrote:
> All,
>
> One of my colleagues on the Fortran Standardization Committee asked me the
> following question:
>
> "People are still not too familiar with the new GCC numbering scheme. My
> impression is that 5.2 is just a maintenance update of 5.1. Howev
Snapshot gcc-5-20151006 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20151006/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
> So in general, it's really not safe to mark a constraint that accepts
> only far memory as "memory constraint" with current reload.
>
> Note that *not* marking the constraint as memory constraint actually
> does not prevent reload from fixing up illegitimate addresses, so you
> shouldn't really
10 matches
Mail list logo
