On Tue, Jan 20, 2015 at 3:26 AM, Sandra Loosemore
wrote:
>> I've noticed that the GCC user documentation is quite inconsistent about
>> the name(s) it uses for i386/x86-64/etc targets. invoke.texi has a
>> section for "i386 and x86-64 Options", but in other places the manual
>> uses x86, X86, i?
Hi,
I have a strange problem with extremely large procedures when generating
64-bit code
I am using gcc 4.9.2 on RHEL6.3 on a 64-thread 4-socket Xeon E7 4820 with 256GB of memory. No avx extensions, using sse option when building the compiler. This particular code is serial. I made measure
On 01/01/2015 05:30 PM, Sandra Loosemore wrote:
I've noticed that the GCC user documentation is quite inconsistent about
the name(s) it uses for i386/x86-64/etc targets. invoke.texi has a
section for "i386 and x86-64 Options", but in other places the manual
uses x86, X86, i?86, i[34567]86, x86_6
On Mon, 19 Jan 2015, Jakub Jelinek wrote:
> On Mon, Jan 19, 2015 at 05:32:39PM +, Jonathan Wakely wrote:
> > I would like to commit these two patches which complete the C++11
> > library implementation:
> >
> > https://gcc.gnu.org/ml/gcc-patches/2015-01/msg01694.html
> > https://gcc.gnu.org/m
On Mon, Jan 19, 2015 at 1:17 AM, Richard Biener wrote:
>
> Status
> ==
>
> The trunk is now in "Stage 4" which means it is open for regression
> and documentation fixes only, like if it were a release branch.
>
> Please concentrate on getting P1 bugs fixed and provide help in
> confirming and
On Mon, Jan 19, 2015 at 05:32:39PM +, Jonathan Wakely wrote:
> I would like to commit these two patches which complete the C++11
> library implementation:
>
> https://gcc.gnu.org/ml/gcc-patches/2015-01/msg01694.html
> https://gcc.gnu.org/ml/gcc-patches/2015-01/msg01648.html
>
> And this one t
On 19 January 2015 at 18:05, Ulrich Drepper wrote:
>> https://gcc.gnu.org/ml/gcc-patches/2015-01/msg01694.html
>
> Just a nit. Why wouldn't you check the value of the variable after
> the assignment in the test case?
Umm, just because I'm dumb? :-)
I'll make that change to my local branch, thanks
On Mon, Jan 19, 2015 at 12:32 PM, Jonathan Wakely wrote:
> I would like to commit these two patches which complete the C++11
> library implementation:
I would definitely be in favor.
> https://gcc.gnu.org/ml/gcc-patches/2015-01/msg01694.html
Just a nit. Why wouldn't you check the value of the
I compile and run my program inside Emacs (M-x compile) with
gcc 5.0.0 20150112 using `-fsanitize=bounds'. Although
this Emacs buffer is technically a tty, but it is `dumb' and does not
handle colors properly.
The gcc info concerning `-fsanitize=address' hints that there is a
parameter ASAN_OP
On 19 January 2015 at 09:17, Richard Biener wrote:
>
> Status
> ==
>
> The trunk is now in "Stage 4" which means it is open for regression
> and documentation fixes only, like if it were a release branch.
>
> Please concentrate on getting P1 bugs fixed and provide help in
> confirming and analy
On 01/17/15 07:34, Gary Funck wrote:
On 01/14/15 23:15:59, Jeff Law wrote:
Sounds good. I think just starting with the list & creating the buckets
with the list. Then post here and we'll iterate and try to nail that down
before you start moving everything in the .texi file.
Something to cons
Status
==
The trunk is now in "Stage 4" which means it is open for regression
and documentation fixes only, like if it were a release branch.
Please concentrate on getting P1 bugs fixed and provide help in
confirming and analyzing UNCONFIRMED bugs. For non-primary,
non-secondary targets imp
12 matches
Mail list logo
