https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107307
Bug ID: 107307
Summary: ICE tree check: expected class 'type', have
'exceptional' (error_mark) in
canonicalize_component_ref, at gimplify.cc:2923
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107305
--- Comment #2 from Andrew Pinski ---
The input is invalid gimple to begin with so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304
H.J. Lu changed:
What|Removed |Added
Last reconfirmed||2022-10-18
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100098
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107266
--- Comment #11 from Steve Kargl ---
On Tue, Oct 18, 2022 at 10:40:59AM +, burnus at gcc dot gnu.org wrote:
>
> (b) subroutine bar(x, y, z) bind(C)
> character(kind=4,len=*) :: x
> character(kind=4) :: y(:)
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107305
Bug ID: 107305
Summary: ICE: 'verify_gimple' failed
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107309
Bug ID: 107309
Summary: GNAT does not apply type conversion rules to dependent
expressions of conditional expressions
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107172
--- Comment #41 from H.J. Lu ---
(In reply to Segher Boessenkool from comment #40)
> Let me repeat: A const_int cannot be assigned to a MODE_CC. It has no
> meaning.
> This is invalid RTL. If it ever works, or worked, that is an accident.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107282
Martin Liška changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107296
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107172
--- Comment #42 from Segher Boessenkool ---
(In reply to H.J. Lu from comment #41)
> (In reply to Segher Boessenkool from comment #40)
> > Let me repeat: A const_int cannot be assigned to a MODE_CC. It has no
> > meaning.
> > This is invalid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104166
Jonathan Wakely changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107306
--- Comment #1 from Andrew Pinski ---
I suspect this is invalid gimple without the options supplied in the dg
command.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101476
--- Comment #18 from Stas Sergeev ---
(In reply to Stas Sergeev from comment #5)
> And its running on a stack previously
> poisoned before pthread_cancel().
And the reason for that is because
the glibc in use is the one not built
with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107256
Marek Polacek changed:
What|Removed |Added
Last reconfirmed||2022-10-18
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107310
Bug ID: 107310
Summary: "warning: control reaches end of non-void function"
with a throw under a trivially-true conditional
Product: gcc
Version: 12.1.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107213
--- Comment #1 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:cc694f45087c892e69ebbb177203c708f00b1bc7
commit r13-3365-gcc694f45087c892e69ebbb177203c708f00b1bc7
Author: Marek Polacek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107213
Marek Polacek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107308
Bug ID: 107308
Summary: ICE in expand_fn_using_insn, at internal-fn.cc:153
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107266
--- Comment #13 from Steve Kargl ---
On Tue, Oct 18, 2022 at 10:40:59AM +, burnus at gcc dot gnu.org wrote:
>
> (In reply to kargl from comment #9)
> > Please commit the patch in comment #7. character(kind=4) is not
> > interoperable
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107164
--- Comment #2 from CVS Commits ---
The master branch has been updated by Joseph Myers :
https://gcc.gnu.org/g:f5f1d92fe2e1d75c3fae34497929a1965af704ae
commit r13-3366-gf5f1d92fe2e1d75c3fae34497929a1965af704ae
Author: Joseph Myers
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101764
--- Comment #6 from CVS Commits ---
The master branch has been updated by Joseph Myers :
https://gcc.gnu.org/g:f5f1d92fe2e1d75c3fae34497929a1965af704ae
commit r13-3366-gf5f1d92fe2e1d75c3fae34497929a1965af704ae
Author: Joseph Myers
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107297
--- Comment #4 from Andrew Pinski ---
Being able to mark a comment or otherwise as not markdown is needed as all old
comments will be messed up that way.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107266
--- Comment #12 from Steve Kargl ---
On Tue, Oct 18, 2022 at 05:29:58PM +, sgk at troutmask dot
apl.washington.edu wrote:
>
> % gfcx -c -std=f2018 a.f90
> a.f90:1:30:
>
> 1 | character(kind=4) function bar(x, y, z) bind(C)
> |
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304
--- Comment #8 from Hongtao.liu ---
(In reply to H.J. Lu from comment #7)
> (In reply to Hongtao.liu from comment #6)
> > (In reply to Hongtao.liu from comment #5)
> > > (In reply to H.J. Lu from comment #4)
> > > > Since the default is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107297
--- Comment #5 from Jeff Muizelaar ---
(In reply to Eric Gallager from comment #2)
> I would also want comments to be editable if this gets turned on, in case I
> screw up my formatting... is there a way to allow that in bugzilla?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107164
Joseph S. Myers changed:
What|Removed |Added
Target Milestone|--- |13.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304
--- Comment #6 from Hongtao.liu ---
(In reply to Hongtao.liu from comment #5)
> (In reply to H.J. Lu from comment #4)
> > Since the default is -march=tigerlake, it enables AVX512 in the middle end.
> > When "arch=alderlake" disables AVX512, we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304
--- Comment #7 from H.J. Lu ---
(In reply to Hongtao.liu from comment #6)
> (In reply to Hongtao.liu from comment #5)
> > (In reply to H.J. Lu from comment #4)
> > > Since the default is -march=tigerlake, it enables AVX512 in the middle
> > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107310
Andrew Pinski changed:
What|Removed |Added
Known to fail||12.1.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107310
--- Comment #2 from Andrew Pinski ---
Note the warning happens at -O0 only.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107297
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304
--- Comment #5 from Hongtao.liu ---
(In reply to H.J. Lu from comment #4)
> Since the default is -march=tigerlake, it enables AVX512 in the middle end.
> When "arch=alderlake" disables AVX512, we fails to expand AVX512 to
> non-AVX512
> ISAs.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107297
--- Comment #3 from Andrew Pinski ---
I think for gcc I rather not support markdown because source gets mangled if
not enclosed with ' or '''.
And many folks don't use markdown especially when they are used to plain text.
C++ is the worst where
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106890
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106880
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106877
Richard Biener changed:
What|Removed |Added
Summary|[12/13 Regression] ICE in |[12 Regression] ICE in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014
--- Comment #8 from Sam James ---
FWIW, the Clang counterpart to this bug is
https://github.com/llvm/llvm-project/issues/41959.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78014
Jiang An changed:
What|Removed |Added
CC||de34 at live dot cn
--- Comment #9 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107311
Bug ID: 107311
Summary: New test case gcc.dg/c2x-enum-1.c fails
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304
--- Comment #9 from H.J. Lu ---
(In reply to Hongtao.liu from comment #8)
> (In reply to H.J. Lu from comment #7)
> > (In reply to Hongtao.liu from comment #6)
> > > (In reply to Hongtao.liu from comment #5)
> > > > (In reply to H.J. Lu from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304
--- Comment #10 from Hongyu Wang ---
(In reply to H.J. Lu from comment #9)
> (In reply to Hongtao.liu from comment #8)
> > (In reply to H.J. Lu from comment #7)
> > > (In reply to Hongtao.liu from comment #6)
> > > > (In reply to Hongtao.liu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304
--- Comment #14 from Hongtao.liu ---
(In reply to H.J. Lu from comment #12)
> (In reply to Hongyu Wang from comment #10)
> >
> > Clang works properly as it overrides -march= to any target clones. I suppose
> > we can do similar things in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304
--- Comment #16 from Hongtao.liu ---
(In reply to H.J. Lu from comment #15)
> (In reply to Hongtao.liu from comment #14)
> > (In reply to H.J. Lu from comment #12)
> > > (In reply to Hongyu Wang from comment #10)
> > > >
> > > > Clang works
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96448
--- Comment #3 from Arseny Solokha ---
I cannot reproduce it anymore w/ gcc 13.0.0 20221016 snapshot
(g:6366e3e8847af98d4728d55951534769d034d02a) and w/ gcc 12.2.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96544
--- Comment #1 from Arseny Solokha ---
I cannot reproduce it anymore w/ gcc 13.0.0 20221016 snapshot
(g:6366e3e8847af98d4728d55951534769d034d02a) and w/ gcc 12.2.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97940
--- Comment #5 from Arseny Solokha ---
I cannot reproduce it anymore w/ gcc 13.0.0 20221016 snapshot
(g:6366e3e8847af98d4728d55951534769d034d02a) and w/ gcc 12.2.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90259
--- Comment #1 from Arseny Solokha ---
I cannot reproduce it anymore w/ gcc 13.0.0 20221016 snapshot
(g:6366e3e8847af98d4728d55951534769d034d02a).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304
--- Comment #11 from Hongtao.liu ---
>
> https://godbolt.org/z/v7xT1zahd
The issue is still there without builtin_shuffle
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104611
vfdff changed:
What|Removed |Added
CC||zhongyunde at huawei dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107312
Bug ID: 107312
Summary: [13 Regression] ICE in verify_range, at
value-range.cc:1172, called from range_true_and_false
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304
--- Comment #12 from H.J. Lu ---
(In reply to Hongyu Wang from comment #10)
>
> Clang works properly as it overrides -march= to any target clones. I suppose
> we can do similar things in ix86_valid_target_attribute_p
That will be wrong since
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107313
Bug ID: 107313
Summary: typo in stride_view::_Iterator::operator-
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304
--- Comment #13 from H.J. Lu ---
A simple testcase:
[hjl@gnu-tgl-3 pr107304]$ cat y1.c
typedef struct {
unsigned char v __attribute__((aligned(256))) __attribute__
((vector_size(64 * sizeof(unsigned char;
} stress_vec_u8_64_t;
void
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106222
--- Comment #2 from Hongtao.liu ---
This is fixed by r13-2843-g3db8e9c2422d92
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304
--- Comment #15 from H.J. Lu ---
(In reply to Hongtao.liu from comment #14)
> (In reply to H.J. Lu from comment #12)
> > (In reply to Hongyu Wang from comment #10)
> > >
> > > Clang works properly as it overrides -march= to any target clones.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85964
--- Comment #23 from Arseny Solokha ---
I cannot reproduce it anymore w/ gcc 13.0.0 20221016 snapshot
(g:6366e3e8847af98d4728d55951534769d034d02a) and w/ gcc 12.2.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88596
--- Comment #15 from Arseny Solokha ---
In case it's still worth it to track the underlying issue somewhere, does it
make sense to open a new PR just for the issue highlighted by Vladimir in
comment 8? Otherwise, I suppose this PR can be safely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99706
--- Comment #13 from Arseny Solokha ---
I cannot reproduce it anymore w/ gcc 13.0.0 20221016 snapshot
(g:6366e3e8847af98d4728d55951534769d034d02a) and w/ gcc 12.2, though 11.3 is
still affected.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88132
--- Comment #2 from Arseny Solokha ---
I cannot reproduce it anymore w/ gcc 13.0.0 20221016 snapshot
(g:6366e3e8847af98d4728d55951534769d034d02a) and w/ gcc 12.2.
101 - 160 of 160 matches
Mail list logo
