https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
--- Comment #16 from Andrew Pinski ---
(In reply to AJ D from comment #15)
> Is it fixed in GCC-9.4?
>
> Didn't find PR99334 in
> https://gcc.gnu.org/bugzilla/buglist.
> cgi?bug_status=RESOLVED=FIXED_milestone=9.4
>
> If not, which GCC9.*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
Andrew Pinski changed:
What|Removed |Added
Known to work||10.3.0, 11.1.0, 8.5.0,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
--- Comment #15 from AJ D ---
Is it fixed in GCC-9.4?
Didn't find PR99334 in
https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED=FIXED_milestone=9.4
If not, which GCC9.* release can we expect a fix for it?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
--- Comment #13 from CVS Commits ---
The releases/gcc-8 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:698b03a66e5115c5dd5cf84bbb499e210df3e709
commit r8-10901-g698b03a66e5115c5dd5cf84bbb499e210df3e709
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
--- Comment #12 from CVS Commits ---
The releases/gcc-9 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:c1780b4c6f1c0e91f10d13e70eb17f5d77f22bb0
commit r9-9438-gc1780b4c6f1c0e91f10d13e70eb17f5d77f22bb0
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
--- Comment #11 from CVS Commits ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:f5df18504c1790413f293bfb50d40faa7f1ea860
commit r10-9624-gf5df18504c1790413f293bfb50d40faa7f1ea860
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
--- Comment #10 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:1cdfc98a9981768c475fabf069ba4d3e460deb2a
commit r11-7870-g1cdfc98a9981768c475fabf069ba4d3e460deb2a
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
--- Comment #9 from Jakub Jelinek ---
As I said on the mailing list, the above patch has problems, it relies on the
insn that clobbers_queued_reg_save to be a single hardware instruction so that
a debug info consumer or unwinding can't stop "in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
--- Comment #8 from Jakub Jelinek ---
I wonder about:
--- gcc/dwarf2cfi.c.jj 2021-03-02 11:25:47.217727061 +0100
+++ gcc/dwarf2cfi.c 2021-03-23 17:34:58.240281522 +0100
@@ -2705,12 +2705,15 @@ scan_trace (dw_trace_info *trace, bool e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
--- Comment #7 from Jakub Jelinek ---
#c6 reproduces even on current trunk with
-fno-tree-sink -O3 -fPIC -fomit-frame-pointer -fno-strict-aliasing
-mstackrealign
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
--- Comment #6 from AJ D ---
Test Case:
--
typedef long int intptr_t;
typedef unsigned long int uintptr_t;
typedef intptr_t DummyType14;
typedef intptr_t DummyType8;
typedef struct DummyType15IntT DummyType15T;
typedef struct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
--- Comment #5 from AJ D ---
Created attachment 50437
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50437=edit
Function _func_with_dwarf_issue_ should demonstrate the issue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
AJ D changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
--- Comment #2 from AJ D ---
The problem seems to have been addressed in gcc-8.x, at least in this
particular function.
I could reproduce this issue in gcc-7.4, but not with gcc-8.2, as can be seen
below.
Will have to check if this issue is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
17 matches
Mail list logo
