http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54826
Bug #: 54826
Summary: gdb test case failure (bs15503) due to gaps in lexical
block
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIR
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54826
Andreas Arnez changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #4 from Andr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54887
Bug #: 54887
Summary: gdb test case failure with mi-var-rtti
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: major
P
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54887
--- Comment #2 from Andreas Arnez 2012-10-10
17:14:32 UTC ---
Right. I've checked that the new upstream gcc with r192285 fixes the problem.
Thanks!
BTW, while investigating this I wondered why g++ wraps all locals in a lexical
block in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54887
Andreas Arnez changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|I
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54887
--- Comment #5 from Andreas Arnez 2012-10-24
17:51:44 UTC ---
(In reply to comment #4)
> <2><32e>: Abbrev Number: 27 (DW_TAG_lexical_block)
> <32f> DW_AT_low_pc : 0x400758
> <337> DW_AT_high_pc : 0x38 0x0
> <3><3
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: arnez at linux dot vnet.ibm.com
Target Milestone: ---
GCC emits DW_OP_piece for vector registers on s390x in (at least) two
different incompatible ways:
(1) When describing a float field
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192
--- Comment #11 from Andreas Arnez ---
Any news here? AFAIK the problem still exists.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192
--- Comment #16 from Andreas Arnez ---
(In reply to Manuel López-Ibáñez from comment #15)
> (In reply to Andreas Arnez from comment #11)
> > Any news here? AFAIK the problem still exists.
>
> I still think the solution in comment #10 is the lea
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192
--- Comment #20 from Andreas Arnez ---
Posted a patch that is not as ambitious as completely getting rid of
input_location, but also doesn't require a new function like
c_parser_peek_token_keep_input_location():
https://gcc.gnu.org/ml/gcc-patc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192
--- Comment #21 from Andreas Arnez ---
(In reply to Andreas Arnez from comment #20)
> Posted a patch that is not as ambitious as completely getting rid of
> input_location, but also doesn't require a new function like
> c_parser_peek_token_keep_i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192
--- Comment #22 from Andreas Arnez ---
Here's another version of the fix:
https://gcc.gnu.org/ml/gcc-patches/2015-11/msg00368.html
It addresses an issue with the previous version that was brought up by Bernd
Schmidt: A breakpoint on the "whi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192
Andreas Arnez changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: arnez at linux dot vnet.ibm.com
With current upstream gcc, the following commands do not yield the expected
output:
echo 'void f (const volatile int x) { }' | gcc -xc -c -g -o foo.o -
readelf -wi fo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63300
Andreas Arnez changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63300
Andreas Arnez changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #6 from Andreas Arnez
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68603
--- Comment #2 from Andreas Arnez ---
Right, the regression is caused by r230979 -- sorry about that. I've posted a
suggested fix:
https://gcc.gnu.org/ml/gcc-patches/2015-11/msg03502.html
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: arnez at linux dot vnet.ibm.com
Target Milestone: ---
"tst.c":
unsigned __int128
foo (unsigned long a, unsigned long b)
{
unsigned __int128 x = (unsigned __int
: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: arnez at linux dot vnet.ibm.com
Target Milestone: ---
This bug causes a number of failures in the GDB test suite, e.g. with
checkpoint.exp. I can reproduce it with the command line:
gcc -fdump-tree-gimple-lineno -o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192
Andreas Arnez changed:
What|Removed |Added
CC||dmalcolm at redhat dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192
--- Comment #7 from Andreas Arnez ---
(In reply to David Malcolm from comment #3)
> The issue seems to be in here in c_parser_for_statement:
>
> warn_for_misleading_indentation (for_loc, body_loc,
> c_parser_p
21 matches
Mail list logo
