https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70188
John David Anglin changed:
What|Removed |Added
CC||danglin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63679
alalaw01 at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70188
--- Comment #1 from deller at gmx dot de ---
Created attachment 37939
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37939=edit
preprocessed source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70189
Bug ID: 70189
Summary: Combine constant-pool logic from gimplify + SRA
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70188
Bug ID: 70188
Summary: gcc 4.9+ miscompiles code on hppa
Product: gcc
Version: 4.9.4
URL: https://patchwork.kernel.org/patch/8402441/
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70166
--- Comment #2 from Alexander Cherepanov ---
On 03/11/2016 12:16 PM, rguenth at gcc dot gnu.org wrote:
> You are not accessing through the union type but through a pointer to double
> and int because u.a and p->d decay to a pointer:
>
>*(int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70147
--- Comment #2 from Martin Liška ---
I tries to isolate the issue (attached patch reduces just the problematic
instrumentation):
$ g++ metafunction.ii -fsanitize=vptr -fdump-tree-optimized -g -O1
-flifetime-dse=0
binfo modified (zeroed)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70048
--- Comment #17 from Wilco ---
(In reply to Jiong Wang from comment #16)
> * for the second patch at #c10, if we always do the following no matter
> op0 is virtual & eliminable or not
>
> "op1 = force_operand (op1, NULL_RTX);"
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45076
--- Comment #7 from Dominique d'Humieres ---
Created attachment 37938
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37938=edit
Proposed test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70187
Tobias Burnus changed:
What|Removed |Added
Target Milestone|--- |6.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70187
Bug ID: 70187
Summary: [6 Regression] ICE (segfault) in lto1 with
-Wsuggest-final-methods/-Wsuggest-final-types
Product: gcc
Version: 6.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70178
--- Comment #3 from rguenther at suse dot de ---
On Fri, 11 Mar 2016, zackw at panix dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70178
>
> --- Comment #2 from Zack Weinberg --- That was
> my working hypothesis as well.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70177
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68963
Bug 68963 depends on bug 70177, which changed state.
Bug 70177 Summary: [6 Regression] ICE in extract_ops_from_tree starting with
r233660
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70177
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70177
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Fri Mar 11 12:28:50 2016
New Revision: 234140
URL: https://gcc.gnu.org/viewcvs?rev=234140=gcc=rev
Log:
PR tree-optimization/70177
* gimple-expr.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70174
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70169
Jakub Jelinek changed:
What|Removed |Added
Summary|[4.9/5/6 Regression] ICE at |[4.9/5 Regression] ICE at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70013
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70178
--- Comment #2 from Zack Weinberg ---
That was my working hypothesis as well. Isn't there some way we can annotate
s->data to reassure the compiler that *this* char* doesn't alias? I don't know
enough about the guts of std::string to know
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70013
--- Comment #13 from alalaw01 at gcc dot gnu.org ---
Author: alalaw01
Date: Fri Mar 11 12:08:01 2016
New Revision: 234138
URL: https://gcc.gnu.org/viewcvs?rev=234138=gcc=rev
Log:
Fix PR/70013
gcc:
PR tree-optimization/70013
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70174
--- Comment #10 from Jakub Jelinek ---
Author: jakub
Date: Fri Mar 11 12:07:01 2016
New Revision: 234137
URL: https://gcc.gnu.org/viewcvs?rev=234137=gcc=rev
Log:
PR rtl-optimization/70174
* expmed.c (store_bit_field_using_insv):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70169
--- Comment #4 from Jakub Jelinek ---
Author: jakub
Date: Fri Mar 11 12:05:58 2016
New Revision: 234136
URL: https://gcc.gnu.org/viewcvs?rev=234136=gcc=rev
Log:
PR tree-optimization/70169
* tree-ssa-loop.c (gen_lsm_tmp_name):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65178
--- Comment #14 from Leon Winter ---
I am not sure how smart he diagnostic of GCC is supposed to be it seems that
the source base of GCC itself has fallen victim to the false warning.
The following commit fixes a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70186
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70186
Bug ID: 70186
Summary: RFE: better handling of misspelled attributes
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70161
vries at gcc dot gnu.org changed:
What|Removed |Added
Attachment #37918|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70161
--- Comment #3 from vries at gcc dot gnu.org ---
(In reply to Richard Biener from comment #2)
> Hum, what does it do if only guarding the !pass->graph_dump_initialized
> check?
That fixes the segfault, but we run into another segfault with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70184
--- Comment #4 from Richard Biener ---
With TER we delay expanding of (unsigned b) until you require its expansion
during asm op expansion (and thus may be interleaved with asm expansion code).
I believe we had this issue in the past for other
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70170
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70160
Ilya Enkovich changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70160
--- Comment #8 from Ilya Enkovich ---
Author: ienkovich
Date: Fri Mar 11 11:25:29 2016
New Revision: 234135
URL: https://gcc.gnu.org/viewcvs?rev=234135=gcc=rev
Log:
gcc/
PR target/70160
* config/i386/i386.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70171
--- Comment #6 from rguenther at suse dot de ---
On Fri, 11 Mar 2016, ubizjak at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70171
>
> --- Comment #5 from Uroš Bizjak ---
> (In reply to Richard Biener from comment #4)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70171
--- Comment #5 from Uroš Bizjak ---
(In reply to Richard Biener from comment #4)
> Created attachment 37935 [details]
> patch
>
> Patch I am testing.
+ /* { dg-final { scan-assembler-not "\[er\]sp" { target x86_64-*-* } } } */
You should
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70182
--- Comment #6 from Markus Trippelsdorf ---
https://llvm.org/svn/llvm-project/libcxxabi/trunk/src/cxa_demangle.cpp
https://github.com/ianlancetaylor/demangle
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70171
--- Comment #4 from Richard Biener ---
Created attachment 37935
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37935=edit
patch
Patch I am testing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70182
--- Comment #5 from Markus Trippelsdorf ---
(In reply to Andrew Pinski from comment #4)
> >Ian's go demangler and the libcxxabi demangler also are unable to demangle
> >these symbols.
>
> Because they are all the same code ...
No, they are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70182
--- Comment #4 from Andrew Pinski ---
>Ian's go demangler and the libcxxabi demangler also are unable to demangle
>these symbols.
Because they are all the same code ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70013
--- Comment #12 from alalaw01 at gcc dot gnu.org ---
Thanks, Martin - yes, I see.
Patch posted at https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00680.html after
full regtest.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70170
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70174
--- Comment #9 from Uroš Bizjak ---
(In reply to Uroš Bizjak from comment #4)
> (In reply to Jakub Jelinek from comment #3)
> > Though, aarch64 ICEs in the same place, so this is likely not an i386
> > backend issue.
>
> This is an issue with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70171
Richard Biener changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70185
--- Comment #1 from vries at gcc dot gnu.org ---
Created attachment 37934
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37934=edit
tentative patch
No more warnings, also for rtl:
...
$ rm *.c.* ; gcc test.c -O2 -S -fdump-tree-all-graph
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70182
Markus Trippelsdorf changed:
What|Removed |Added
Status|WAITING |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70184
--- Comment #3 from ktkachov at gcc dot gnu.org ---
(In reply to Andrew Pinski from comment #2)
> Does -fno-ter fix the issue?
> How does the tree level look?
You mean -fno-tree-ter?
That gives:
foo:
@ args = 0, pretend = 0, frame = 0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70185
Bug ID: 70185
Summary: fdump-tree-all-graph produces invalid dot files
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70177
--- Comment #5 from Jakub Jelinek ---
Created attachment 37933
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37933=edit
gcc6-pr70177.patch
Untested fix. The questions about latent issues, where the upper bound
expression comes from and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70184
--- Comment #2 from Andrew Pinski ---
Does -fno-ter fix the issue?
How does the tree level look?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70184
--- Comment #1 from ktkachov at gcc dot gnu.org ---
Things are bad already at expand time:
2: r111:SI=r0:SI
3: r112:SF=r1:SF
4: NOTE_INSN_FUNCTION_BEG
7: r0:SI=r111:SI
8: r0:SF=r112:SF
9: r0:SI=call [`__aeabi_f2uiz']
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70183
--- Comment #2 from vries at gcc dot gnu.org ---
(In reply to vries from comment #1)
> Created attachment 37932 [details]
> tentative patch
Which has the desired effect:
...
$ rm *.c.* ; gcc test.c -S -fdump-rtl-all-slim -mavx -mvzeroupper
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70174
--- Comment #8 from Jakub Jelinek ---
(In reply to Andrew Pinski from comment #7)
> Comment on attachment 37931 [details]
> gcc6-pr70174.patch
>
> + tmp = gen_lowpart (op_mode, force_reg (GET_MODE (value),
> +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70183
--- Comment #1 from vries at gcc dot gnu.org ---
Created attachment 37932
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37932=edit
tentative patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70184
Bug ID: 70184
Summary: Exlpicit register variables overwritten by conversion
libcall
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Keywords: wrong-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70183
Bug ID: 70183
Summary: fdump-rtl-all-flags doesn't have impact on vzeroupper
pass
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: minor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70174
--- Comment #7 from Andrew Pinski ---
Comment on attachment 37931
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37931
gcc6-pr70174.patch
+ tmp = gen_lowpart (op_mode, force_reg (GET_MODE (value),
+
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70174
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70174
--- Comment #5 from Andrew Pinski ---
(In reply to Jakub Jelinek from comment #3)
> Though, aarch64 ICEs in the same place, so this is likely not an i386
> backend issue.
Though the revision where the failure starts says something about what to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70174
--- Comment #4 from Uroš Bizjak ---
(In reply to Jakub Jelinek from comment #3)
> Though, aarch64 ICEs in the same place, so this is likely not an i386
> backend issue.
This is an issue with insv handling infrastructure. The problem is in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70177
Richard Biener changed:
What|Removed |Added
Blocks||68963
--- Comment #4 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70174
--- Comment #3 from Jakub Jelinek ---
Though, aarch64 ICEs in the same place, so this is likely not an i386 backend
issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70166
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70169
--- Comment #3 from Richard Biener ---
Maybe finally get rid of the gcc_unreachable () by providing a sane default for
this non-critical fn?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70174
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70170
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70171
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70169
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70174
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |6.0
--- Comment #1 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70176
Richard Biener changed:
What|Removed |Added
Target||x86_64-pc-cygwin
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70178
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70146
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70182
--- Comment #2 from Taewook Oh ---
Here is a link to the preprocessed text: http://paste.ubuntu.com/15346235/
As I wrote in the description, it seems pretty clear that demangler applies an
incorrect rule to demangle expression. For "srT_oncl",
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70181
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70159
--- Comment #10 from rguenther at suse dot de ---
On Thu, 10 Mar 2016, spop at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70159
>
> --- Comment #9 from Sebastian Pop ---
> Created attachment 37927
> -->
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70182
Markus Trippelsdorf changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
101 - 173 of 173 matches
Mail list logo