http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60013
--- Comment #17 from Jan Hubicka ---
Author: hubicka
Date: Thu Feb 6 07:39:24 2014
New Revision: 207529
URL: http://gcc.gnu.org/viewcvs?rev=207529&root=gcc&view=rev
Log:
PR middle-end/60013
* ipa-inline-analysis.c (compute_bb_predicates
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55791
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment #
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55903
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57544
Marek Polacek changed:
What|Removed |Added
Status|WAITING |RESOLVED
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60087
Marek Polacek changed:
What|Removed |Added
Keywords||diagnostic
Status|UNCONFIRMED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60089
Bug ID: 60089
Summary: Complex arithmetic instructions
Product: gcc
Version: 4.8.2
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: rtl-optimization
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #8 from Jacob Abel ---
Seriously? Look, you falsely assumed it was mingw only. Jerry reproduced the
problem on linux as well. Excuse me for not knowing to post the backtrace. I
come here to post a legitimate bug and all you've done is
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54041
Jeffrey A. Law changed:
What|Removed |Added
Priority|P4 |P5
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #7 from kargl at gcc dot gnu.org ---
(In reply to Jacob Abel from comment #6)
> (In reply to Steve Kargl from comment #5)
> > What output file? gcc_flags.txt does not show a segfault
> > or a debugger backtrace.
>
> It shows that I wa
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #16 from H. Peter Anvin ---
Josh: nullptr pollutes the C user namespace, so it's not an option.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #6 from Jacob Abel ---
(In reply to Steve Kargl from comment #5)
> What output file? gcc_flags.txt does not show a segfault
> or a debugger backtrace.
It shows that I was not using MinGW, as you assumed. Here's the gdb output:
jake@
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #5 from Steve Kargl ---
On Thu, Feb 06, 2014 at 02:25:27AM +, thatcadguy at gmail dot com wrote:
>
> If you bothered to look at the gcc output file, you'd see that I tested it on
> Linux as well. This is a GCC and MinGW problem. T
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #3 from Jacob Abel ---
If you bothered to look at the gcc output file, you'd see that I tested it on
Linux as well. This is a GCC and MinGW problem. The code segfaults on both
platforms with both compilers.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
Bug ID: 60088
Summary: Segfault when using quad precision and -march=native
on gfortran
Product: gcc
Version: 4.7.3
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088
--- Comment #1 from Jacob Abel ---
Created attachment 32062
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32062&action=edit
gcc -v output and march=native flags
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60073
--- Comment #8 from Eric Botcazou ---
> Note that powerpc64-gcc passes fp arguments corresponding to the ellipsis
> part of variadic functions in both the parameter save area and fp registers,
> contrary to the ABI which says they just go in the p
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60087
Bug ID: 60087
Summary: Incorrect column number for -Wsign-compare
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #15 from Josh Triplett ---
(In reply to Tom Tromey from comment #14)
> (In reply to Josh Triplett from comment #11)
> > Personally, I'd actually suggest merging the two in GCC, and always issuing
> > both sets of warnings. I'd also su
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60013
--- Comment #16 from Pat Haugen ---
I tried the patch from Comment 15 and was able to build/run the benchmark
successfully.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60073
--- Comment #7 from Alan Modra ---
The variadic support in libfii is fairly recent. And yes, it might have been
there earlier if the testcases actually tested what they were suppose to test!
Note that powerpc64-gcc passes fp arguments correspond
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60086
Bug ID: 60086
Summary: suboptimal asm generated for a loop (store/load false
aliasing)
Product: gcc
Version: 4.7.3
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56458
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60085
--- Comment #1 from Marek Polacek ---
Even gcc34 ICEs on this, not a regression.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60085
Bug ID: 60085
Summary: ICE in get_frame_type on weird code
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60073
--- Comment #6 from Eric Botcazou ---
It's a bad interaction between closures and variadic functions (and the other
test cls_longdouble_va.c passes by accident), which will require the SPARC-V9
code to define FFI_TARGET_SPECIFIC_VARIADIC. I'm a b
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53123
--- Comment #1 from Marek Polacek ---
Author: mpolacek
Date: Wed Feb 5 21:06:56 2014
New Revision: 207524
URL: http://gcc.gnu.org/viewcvs?rev=207524&root=gcc&view=rev
Log:
PR c/53123
c-family/
* c-omp.c (c_finish_omp_atomic): Remove unre
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53123
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53123
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42174
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56044
--- Comment #11 from joseph at codesourcery dot com ---
On Wed, 5 Feb 2014, dpapavas at gmail dot com wrote:
> I see, thanks for the advice. Just a clarification: you mean that I should CC
> the personal email of the two objc maintainers as I fi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60072
--- Comment #4 from Zhendong Su ---
(In reply to Jakub Jelinek from comment #3)
> It is fixed by the same patch, and is the same problem. If one of the two
> PRs ever worked with optimize attribute, it was purely by accident.
Okay, thanks Jakub!
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56044
--- Comment #10 from Dimitris Papavasiliou ---
I see, thanks for the advice. Just a clarification: you mean that I should CC
the personal email of the two objc maintainers as I find it from the page
below, correct?
http://gcc.gnu.org/svn/gcc/bra
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #14 from Tom Tromey ---
(In reply to Josh Triplett from comment #11)
> Without -Wcast-to-as, you won't get a warning for unforced casts that add an
> address space.
Thanks!
> Personally, I'd actually suggest merging the two in GCC,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46112
Marek Polacek changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #13 from Josh Triplett ---
(In reply to H. Peter Anvin from comment #8)
> Arguably the *right* way to solve that would be to support __null for C as
> well as for C++.
__null or nullptr?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #12 from Josh Triplett ---
(In reply to Tom Tromey from comment #9)
> (In reply to Josh Triplett from comment #7)
>
> > I can't think of a legitimate reason to have a null pointer constant in a
> > non-zero address space; there's alre
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #11 from Josh Triplett ---
(In reply to Tom Tromey from comment #10)
> Relatedly, could you say what the option "-Wcast-to-as" provides
> beyond the normal warnings about changing address spaces?
> I wonder if this is something I shoul
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60078
--- Comment #5 from Mikael Pettersson ---
(In reply to Eric Botcazou from comment #4)
> > This passes for me on armv5tel-linux-gnueabi with gcc trunk/4.8/4.7, on real
> > HW (Kirkwood), glibc-2.17, linux-3.13 kernel.
>
> Single or multi core?
Si
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60084
--- Comment #8 from Florin Iucha ---
Andrew,
You are correct! Sorry, I have missed the lack of 'extern'. I noticed the
warning, but did not heed it ;(
florin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60084
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60084
--- Comment #6 from Florin Iucha ---
Andrew,
Is that a general comment regarding Linaro GCC build, or do you have more
specific information about some of their changes that might have an impact on
compiling the source code I am referencing in thi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60084
--- Comment #5 from Florin Iucha ---
Created attachment 32059
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32059&action=edit
Preprocessed source file (both 4.7.4 and 4.8.3 produce the same .i file)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60084
--- Comment #4 from Andrew Pinski ---
Do you have the preprocessed source?
>Using GCC built by Linaro.
Also you should be reporting this bug to them as they are the ones who modified
the source.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60084
--- Comment #3 from Florin Iucha ---
gcc version 4.7.4 20130913 (release) [ARM/embedded-4_7-branch revision 202601]
(GNU Tools for ARM Embedded Processors) generates the same code as 4.7.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59575
Richard Henderson changed:
What|Removed |Added
Assignee|rth at gcc dot gnu.org |jakub at gcc dot gnu.org
--- C
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52727
--- Comment #24 from Jakub Jelinek ---
(In reply to Richard Henderson from comment #23)
> Re-fixed. That is, the broken commit reverted and another fix
> for that other problem (with apparently no PR) applied.
For the record, the other problem w
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60084
--- Comment #2 from Florin Iucha ---
Created attachment 32058
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32058&action=edit
objdump of binary built with gcc-4.8.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60084
--- Comment #1 from Florin Iucha ---
Created attachment 32057
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32057&action=edit
objdump of binary built with gcc-4.7.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60084
Bug ID: 60084
Summary: GCC 4.8.3 miscompiles code on ARM at -Os optimization
level
Product: gcc
Version: 4.8.3
Status: UNCONFIRMED
Severity: normal
Pri
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52727
Richard Henderson changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60078
Eric Botcazou changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #4 from Eric Botcazou --
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52727
--- Comment #22 from Richard Henderson ---
Author: rth
Date: Wed Feb 5 18:42:19 2014
New Revision: 207518
URL: http://gcc.gnu.org/viewcvs?rev=207518&root=gcc&view=rev
Log:
PR debug/52727
* combine-stack-adj.c: Revert r206943.
*
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59984
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59176
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment #
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60082
--- Comment #3 from Dominique d'Humieres ---
> According to http://gcc.gnu.org/ml/gcc-regression/2014-02/msg1.html
> this appeared between r207378 and r207382 (candidates r207382 or r207383).
(candidates r207382 or r207383) should be r207382
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60078
--- Comment #3 from Mikael Pettersson ---
This passes for me on armv5tel-linux-gnueabi with gcc trunk/4.8/4.7, on real HW
(Kirkwood), glibc-2.17, linux-3.13 kernel.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59305
--- Comment #17 from Dominique d'Humieres ---
Created attachment 32056
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32056&action=edit
sampling of one of the runs.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59305
--- Comment #16 from Dominique d'Humieres ---
> Even that seems to require ifunc support, which isn't supported on Solaris
> even with gld.
AFAICR ifunc is not supported on darwin.
I have posted at http://gcc.gnu.org/ml/gcc-testresults/2014-02/m
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60082
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60082
Dominique d'Humieres changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60073
--- Comment #5 from Eric Botcazou ---
Btw, in the introduction section of the documentation, there is:
"Compilers for high level languages generate code that follow certain
conventions. These conventions are necessary, in part, for separate
comp
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59753
--- Comment #6 from Vincent Lefèvre ---
(In reply to Manuel López-Ibáñez from comment #5)
> (In reply to Vincent Lefèvre from comment #4)
> > There's still an inconsistency without -Wpedantic, which is the point of
> > this bug. I've changed the b
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #10 from Tom Tromey ---
Relatedly, could you say what the option "-Wcast-to-as" provides
beyond the normal warnings about changing address spaces?
I wonder if this is something I should be pulling in as well.
"man sparse" doesn't reall
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57748
--- Comment #54 from Bernd Edlinger ---
(In reply to Marek Polacek from comment #53)
> So fixed on the trunk?
yes, fixed on trunk.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #9 from Tom Tromey ---
(In reply to Josh Triplett from comment #7)
> I can't think of a legitimate reason to have a null pointer constant in a
> non-zero address space; there's already a null pointer constant, NULL,
> effectively in a
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60083
Bug ID: 60083
Summary: Duplicate conversion warnings from negative integer to
unsigned type (gcc-4.3 emits only one warning)
Product: gcc
Version: 4.9.0
Status: UNCONFIRME
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56044
--- Comment #9 from joseph at codesourcery dot com ---
After sending a patch to gcc-patches, please keep pinging weekly on
gcc-patches with the ObjC maintainers CC:ed, and giving the URL of the
original patch submission, for as long as it takes
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57748
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment #
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59150
--- Comment #6 from Jakub Jelinek ---
Created attachment 32055
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32055&action=edit
gcc49-pr59150.patch
Untested fix for that and various other issues.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60078
--- Comment #2 from Bernd Edlinger ---
it's a real hardware (Altera CyloneV SoC Eva-Board)
with dual core ARMv7
running linux and eglibc
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60082
Balaji V. Iyer changed:
What|Removed |Added
Severity|normal |major
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5
--- Comment #11 from Paulo J. Matos ---
(In reply to Paulo J. Matos from comment #10)
> (In reply to Paulo J. Matos from comment #8)
> >
> > Made a mistake. With the attached test, the final gimple before expand for
> > the loop basic block is:
>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60082
Bug ID: 60082
Summary: Certain Cilk keywords executable Hanging for -O1
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #8 from H. Peter Anvin ---
Arguably the *right* way to solve that would be to support __null for C as well
as for C++.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59737
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment #
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59753
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60078
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59753
Vincent Lefèvre changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|WORKSFOR
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60073
Eric Botcazou changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|ebotcazou at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60047
Paolo Carlini changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60073
Eric Botcazou changed:
What|Removed |Added
Target|sparc*-sun-solaris2.* |sparc*-*-*
Status|UNCONFIRMED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59918
--- Comment #6 from Markus Trippelsdorf ---
(In reply to Jan Hubicka from comment #5)
> Should be the same issue as PR59947
No. Still happens after r207512.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59918
Bug 59918 depends on bug 59947, which changed state.
Bug 59947 Summary: [4.9 Regression] Segmentation fault with #pragma GCC
optimize ("O2"), ICE in get_odr_type
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59947
What|Removed
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58703
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59947
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60072
--- Comment #3 from Jakub Jelinek ---
It is fixed by the same patch, and is the same problem. If one of the two PRs
ever worked with optimize attribute, it was purely by accident.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60081
Bug ID: 60081
Summary: Internal compiler error: Error reporting routines
re-entered.
Product: gcc
Version: 4.7.3
Status: UNCONFIRMED
Severity: major
Pr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #7 from Josh Triplett ---
(In reply to Tom Tromey from comment #6)
> Null pointer constants are treated specially, which makes sense,
> but only if they have type "void *" and are in address space 0.
Otherwise, they're not a null poin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59753
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60062
--- Comment #5 from Zhendong Su ---
(In reply to Jakub Jelinek from comment #4)
> *** Bug 60072 has been marked as a duplicate of this bug. ***
The testcase below is most likely another dup as the only difference is that it
affects the trunk at -
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5
--- Comment #10 from Paulo J. Matos ---
(In reply to Paulo J. Matos from comment #8)
>
> Made a mistake. With the attached test, the final gimple before expand for
> the loop basic block is:
> ;; basic block 5, loop depth 0
> ;;pred:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59947
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Wed Feb 5 15:34:25 2014
New Revision: 207512
URL: http://gcc.gnu.org/viewcvs?rev=207512&root=gcc&view=rev
Log:
PR ipa/59947
* ipa-devirt.c (possible_polymorphic_call_targets): Fix
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58703
--- Comment #2 from Jakub Jelinek ---
Author: jakub
Date: Wed Feb 5 15:32:01 2014
New Revision: 207511
URL: http://gcc.gnu.org/viewcvs?rev=207511&root=gcc&view=rev
Log:
PR c++/58703
* parser.c (cp_parser_omp_declare_reduction): Save and
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60072
--- Comment #2 from Zhendong Su ---
(In reply to Jakub Jelinek from comment #1)
> Seems to be a dup of PR60062.
>
> *** This bug has been marked as a duplicate of bug 60062 ***
Sorry for the dup Jakub, but are you certain about it? Since 60062
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60080
Bug ID: 60080
Summary: gcc.dg/vect/vect-nop-move.c FAILs
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60080
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |4.9.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59305
--- Comment #14 from Iain Sandoe ---
(In reply to r...@cebitec.uni-bielefeld.de from comment #13)
> > --- Comment #12 from Iain Sandoe ---
> [...]
> > Do you repeat the findings we see on Darwin, where a heavily loaded system
> > does
> > not ex
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60076
--- Comment #8 from Richard Biener ---
Author: rguenth
Date: Wed Feb 5 15:14:56 2014
New Revision: 207509
URL: http://gcc.gnu.org/viewcvs?rev=207509&root=gcc&view=rev
Log:
2014-02-05 Richard Biener
PR testsuite/60076
* gcc.dg/vect/pr
1 - 100 of 178 matches
Mail list logo