I routinely build the weekly snapshots and RC's, on x64, arm and aarch64.
The last gcc 8 snapshot and the two recent 7.2 RC's have failed to build
on aarch64 (Raspberry Pi 3, running Arch Linux ARM). I have finally
traced this to the system running out of memory. I guess a recent kernel
update
On 05/27/2017 06:09 PM, Michael Eager wrote:
> On 05/27/2017 01:51 AM, Waldemar Brodkorb wrote:
>> Hi,
>>
>> Buildroot and OpenADK have samples to create a Linux system to be
>> bootup in Qemu system emulation for microblaze architecture.
>>
>> With gcc 6.3 and 7.1 the samples are not working anymo
On 2017.08.09 at 14:05 +0100, Andrew Roberts wrote:
> I routinely build the weekly snapshots and RC's, on x64, arm and aarch64.
>
> The last gcc 8 snapshot and the two recent 7.2 RC's have failed to build on
> aarch64 (Raspberry Pi 3, running Arch Linux ARM). I have finally traced this
> to the sy
On 09/08/17 14:05, Andrew Roberts wrote:
> 2) It would be nice to see some sort of out of memory error, rather than
> just an ICE.
There's nothing we can do: the kernel killed us. We can't emit any
message before we die. (killed) tells you that we were killed, but
we don't know who done it.
--
On 09/08/17 14:05, Andrew Roberts wrote:
I routinely build the weekly snapshots and RC's, on x64, arm and aarch64.
The last gcc 8 snapshot and the two recent 7.2 RC's have failed to
build on aarch64 (Raspberry Pi 3, running Arch Linux ARM). I have
finally traced this to the system running out
On Wed, Aug 9, 2017 at 2:49 PM, Andrew Haley wrote:
> On 09/08/17 14:05, Andrew Roberts wrote:
>> 2) It would be nice to see some sort of out of memory error, rather than
>> just an ICE.
>
> There's nothing we can do: the kernel killed us. We can't emit any
> message before we die. (killed) tell
On Aug 09 2017, Yuri Gribov wrote:
> On Wed, Aug 9, 2017 at 2:49 PM, Andrew Haley wrote:
>> On 09/08/17 14:05, Andrew Roberts wrote:
>>> 2) It would be nice to see some sort of out of memory error, rather than
>>> just an ICE.
>>
>> There's nothing we can do: the kernel killed us. We can't emit
On 08/08/2017 01:38 PM, Steve Ellcey wrote:
> I was wondering if something needs to be done about the gcc.dg/guality tests.
>
> There are two main issues I see with these tests, one is that they are often
> not run during testing and so failures do not show up. I looked into this
> and found that
On 08/06/2017 01:59 AM, Boris Kolpackov wrote:
> Hi,
>
> Currently GCC does not write extracted header dependency information
> if there are errors. However, this can be useful when dealing with
> outdated generated headers that trigger errors which would have been
> resolved if we could update it
On Wed, 9 Aug 2017, Jeff Law wrote:
> This directly reverts part of Joseph's changes from 2009. I'd like to
> hear from him on this change.
The point of those changes was to make cpplib diagnostics use the
compiler's diagnostic machinery rather than a separate set of diagnostic
machinery in c
Snapshot gcc-6-20170809 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20170809/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6
11 matches
Mail list logo
