On Mon, Aug 14, 2017 at 06:22:39PM +0100, Jonathan Wakely wrote:
> On 13 August 2017 at 19:20, Ron wrote:
> >
> > Hi,
> >
> > I'm looking for some clarification of how the __forced_unwind thread
> > cancellation exceptions intersect with noexcept. I've long been a
> > big fan of the __forced_unwin
On 08/14/2017 04:22 PM, Eric Gallager wrote:
I'm emailing this manually to the list because Bugzilla is down and I
can't file a bug on Bugzilla about Bugzilla being down. The error
message looks like this:
Bugzilla and the rest of gcc.gnu.org have been down much of
the afternoon/evening due to
On 08/14/2017 08:09 AM, H.J. Lu wrote:
> Yes, I got the same error with --enable-checking=yes,rtl:
>
> cc1plus: out of memory allocating 56137200 bytes after a total of
> 3139436544 bytes
> make[5]: *** [Makefile:1104: insn-extract.o] Error 1
Thanks for the confirmation. I have a successful x32 b
On 13 August 2017 at 19:20, Ron wrote:
>
> Hi,
>
> I'm looking for some clarification of how the __forced_unwind thread
> cancellation exceptions intersect with noexcept. I've long been a
> big fan of the __forced_unwind idiom, but now that C++14 is the default
> since GCC 6.1, and many methods in
For GCC 8, when --enable-checking=yes,rtl is used with x32 GCC,
I got
cc1plus: out of memory allocating 56137200 bytes after a total of
3139436544 bytes
make[5]: *** [Makefile:1104: insn-extract.o] Error 1
make[5]: *** Waiting for unfinished jobs
gcc-7-branch is OK. Is this expected?
--
H.
On Mon, Aug 14, 2017 at 12:35 AM, Daniel Santos wrote:
> On 08/13/2017 07:05 PM, H.J. Lu wrote:
>> On Sun, Aug 13, 2017 at 3:52 PM, Daniel Santos
>> wrote:
>>> I've setup an x32 test environment using Gentoo in hopes of being able
>>> to both compile and run x32 tests, but I'm having problems ge
On Sun, Aug 13, 2017 at 10:25:14PM +0930, Alan Modra wrote:
> On Sun, Aug 13, 2017 at 03:35:15AM -0700, David Wohlferd wrote:
> > Using "m"(*pStr) as an (unused) input parameter has no effect.
>
> Use "m" (*(const void *)pStr) and ignore the warning, or use
> "m" (*(const struct {char a; char x[];
Status
==
GCC 7.2 has been released and the branch is again open for regression
and documentation fixes. History makes us expect a GCC 7.3 release
at the end of this or the beginning of next year.
Quality Data
Priority # Change from last report
---
The GNU Compiler Collection version 7.2 has been released.
GCC 7.2 is a bug-fix release from the GCC 7 branch
containing important fixes for regressions and serious bugs in
GCC 6.1 with more than 95 bugs fixed since the previous release.
This release is available from the FTP servers listed at:
On Wed, Aug 9, 2017 at 5:59 PM, Jeff Law wrote:
> 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 failure
On 08/13/2017 07:05 PM, H.J. Lu wrote:
> On Sun, Aug 13, 2017 at 3:52 PM, Daniel Santos
> wrote:
>> I've setup an x32 test environment using Gentoo in hopes of being able
>> to both compile and run x32 tests, but I'm having problems getting a
>> successful bootstrap. I'm guessing this is due to
On 08/13/2017 05:52 PM, Daniel Santos wrote:
> cc1plus: out of memory allocating 56137200 bytes after a total of
> 314880 bytes
> make[3]: *** [Makefile:1104: insn-extract.o] Error 1
> make[3]: *** Waiting for unfinished jobs
I apparently misunderstood the "after a total of x" part of the
12 matches
Mail list logo
