https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108842
Bug ID: 108842
Summary: Cannot use enum array with -fno-druntime
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931
--- Comment #13 from Andrew Pinski ---
(In reply to ishikawa,chiaki from comment #11)
> What is exactly the compiler-defined macro when "-Og" is used on the command
> line?
There is not one ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931
--- Comment #11 from ishikawa,chiaki ---
Created attachment 54484
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54484&action=edit
Script to compile the previous source file.
The previous source file ought to be named
't-failure-always-in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931
ishikawa,chiaki changed:
What|Removed |Added
CC||ishikawa at yk dot rim.or.jp
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83286
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92953
--- Comment #5 from Andrew Pinski ---
On x86_64 since the flags get clobbered with almost all instructions. Either
you do the subtraction twice or you use set instruction. GCC choses the later
... I suspect that is a general issue that shows up m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10520
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108841
Bug ID: 108841
Summary: sometimes a < b && c < b is not optimized to MAX
< b
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98966
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98966
--- Comment #3 from Gabriel Ravier ---
Appears to be fixed on trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96930
--- Comment #11 from Gabriel Ravier ---
It appears like this is fixed on trunk, I think ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96692
--- Comment #4 from Andrew Pinski ---
(In reply to Gabriel Ravier from comment #3)
> This seems to be fixed on trunk now, I think ?
On x86_64-linux-gnu yes but on aarch64 it is not optimized just yet:
f(int, int, int):
eor w1, w0, w1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96692
--- Comment #3 from Gabriel Ravier ---
This seems to be fixed on trunk now, I think ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95427
--- Comment #2 from Gabriel Ravier ---
Still appears to be fixed on trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108836
--- Comment #4 from Peter Dimov ---
A compromise between no mutex at all, and a mutex that is silently a no-op,
could be a no-op mutex with [[deprecated]] members, although the atomic_flag is
probably better.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94908
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94899
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19987
Bug 19987 depends on bug 94899, which changed state.
Bug 94899 Summary: Failure to optimize out add before compare with INT_MIN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94899
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94908
--- Comment #3 from Gabriel Ravier ---
Looks like this gives much better output now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94899
--- Comment #7 from Gabriel Ravier ---
I don't know if I've missed something obvious but this still appears to be
fixed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108375
--- Comment #8 from Martin Uecker ---
PATCH: https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612245.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108243
--- Comment #7 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:5fea1be820508e1fbc610d1a54b61c1add33c36f
commit r13-6120-g5fea1be820508e1fbc610d1a54b61c1add33c36f
Author: Patrick Palka
Date: F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97553
--- Comment #6 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:5fea1be820508e1fbc610d1a54b61c1add33c36f
commit r13-6120-g5fea1be820508e1fbc610d1a54b61c1add33c36f
Author: Patrick Palka
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108833
--- Comment #9 from Jakub Jelinek ---
Better reduced testcase that doesn't emit a warning:
struct input_t {
template struct range_t {
friend int &operator>>(int &, range_t &);
range_t(char);
};
int read_s;
void read() {
rang
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108833
--- Comment #8 from Jakub Jelinek ---
Therefore, likely dup of PR106740, but I think we want reduced testcases from
both PRs on the trunk and on branches eventually when it is fixed there too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108833
Jakub Jelinek changed:
What|Removed |Added
Summary|[12 Regression] internal|[11/12 Regression] internal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98334
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
--- Comment #7 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94782
--- Comment #4 from Andrew Pinski ---
The RTL level for x86_64 was fixed with
r11-6456-g4615cde5d7ef281d4b554df411f82ad707f0a54d (aka PR 98334).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94782
Andrew Pinski changed:
What|Removed |Added
Keywords||TREE
--- Comment #3 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94782
--- Comment #2 from Gabriel Ravier ---
Appears to be fixed on trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108833
Jakub Jelinek changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108840
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108840
Bug ID: 108840
Summary: Aarch64 doesn't optimize away shift counter masking
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108833
--- Comment #5 from Jakub Jelinek ---
20220507 works (Fedora 12.1.1-1), 20230210 ICEs, on godbolt 12.2 ICEs
(supposedly 20220819), 20220628 ICEs (Fedora 12.1.1-2).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108833
Jakub Jelinek changed:
What|Removed |Added
Keywords|needs-reduction |
--- Comment #4 from Jakub Jelinek ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107949
--- Comment #6 from Segher Boessenkool ---
We generate loads into QImode regs, so we need to explicitly convert it to
whatever larger mode is wanted later. We also have define_insns to do a
zero-extended load directly into a bigger pseudo, but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108833
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108833
Marek Polacek changed:
What|Removed |Added
Keywords|needs-bisection |
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107949
Peter Bergner changed:
What|Removed |Added
CC||bergner at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107925
Martin Jambor changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jamborm at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108839
--- Comment #1 from Andrew Pinski ---
Note the SLP vectorizer should kick in for most cases of manually unrolled
loops.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108839
Bug ID: 108839
Summary: Option for rerolling loops
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: tree-optimiza
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108838
Bug ID: 108838
Summary: [OpenMP] Array section of allocatable deferred-string
has the wrong offset for the data component
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108831
Uroš Bizjak changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108831
--- Comment #3 from CVS Commits ---
The master branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:6245441e124846d0c3551f312d2feef598fe251c
commit r13-6118-g6245441e124846d0c3551f312d2feef598fe251c
Author: Uros Bizjak
Date: Fri F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108819
--- Comment #4 from Jakub Jelinek ---
(In reply to Richard Biener from comment #3)
> --- a/gcc/tree-ssa-reassoc.cc
> +++ b/gcc/tree-ssa-reassoc.cc
> @@ -2950,6 +2950,9 @@ update_range_test (struct range_entry *range, struct
> range_entry *otherr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90838
--- Comment #21 from Wilco ---
(In reply to Gabriel Ravier from comment #19)
> If the original code being branchless makes it faster, wouldn't that imply
> that we should use the table-based implementation when generating code for
> `__builtin_c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108836
--- Comment #3 from Jonathan Wakely ---
Whatever we do it won't help them, as they're using libstdc++ headers from gcc
6.3
It's possible to have a gcc build that has limited support for threading, but
not enough to support C++11 std::mutex, std
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108836
--- Comment #2 from Peter Dimov ---
That's good to hear, but I don't think the issue is specific to mingw32. The
other report, https://github.com/boostorg/system/issues/92, was about "B&R
PLC", whatever this means. :-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108836
--- Comment #1 from Andrew Pinski ---
mingw32 is no longer defaults to a single threaded and std::mutex is supported
there on the trunk for GCC 13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108837
Bug ID: 108837
Summary: Deferred string length component of DT + array section
passes the wrong array elements
Product: gcc
Version: 13.0
Status: UNCONFIRMED
K
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108836
Bug ID: 108836
Summary: std::mutex disappears in single-threaded libstdc++
builds
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108805
Uroš Bizjak changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108805
Uroš Bizjak changed:
What|Removed |Added
CC||avieira at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108805
--- Comment #3 from CVS Commits ---
The master branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:6ac3ebed5ffbac0d81c5a1d0cb1e345cfad202a8
commit r13-6117-g6ac3ebed5ffbac0d81c5a1d0cb1e345cfad202a8
Author: Uros Bizjak
Date: Fri F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108834
--- Comment #5 from Martin Liška ---
Thank you Jakub for the investigation. I'm saying yes, using symbol names from
debuginfo seems to me a nice improvement. Lemme take a look at it..
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90838
--- Comment #20 from Jakub Jelinek ---
No, because __builtin_ctz is branchless too, it just has UB when the argument
is 0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108834
--- Comment #4 from Jakub Jelinek ---
https://reviews.llvm.org/D127552
So I guess we need to look also if (and if not, why not) we get the same
symbolization from debug info and drop the location stuff there.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90838
--- Comment #19 from Gabriel Ravier ---
(In reply to Jakub Jelinek from comment #14)
> The patch does:
> + bool zero_ok = CTZ_DEFINED_VALUE_AT_ZERO (TYPE_MODE (type), ctzval)
> == 2;
> +
> + /* Skip if there is no value defined at zero,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108834
--- Comment #3 from Jakub Jelinek ---
This is in the arrays passed to __asan_{,un}register_globals.
Now, we emit
/* Build
struct __asan_global
{
const void *__beg;
uptr __size;
uptr __size_with_redzone;
const void *__na
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90838
--- Comment #18 from Jakub Jelinek ---
It is generally a win for cases where the condition can't be predicted, while
if it can, jumps are much better. We have dozens or hundreds of PRs about this
in either direction on x86.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108817
Martin Liška changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90838
--- Comment #17 from Wilco ---
(In reply to Jakub Jelinek from comment #16)
> (In reply to Wilco from comment #15)
> > It would make more sense to move x86 backends to CTZ_DEFINED_VALUE_AT_ZERO
> > == 2 so that you always get the same result even
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108226
--- Comment #2 from Martin Jambor ---
(In reply to Richard Biener from comment #1)
>
> so somehow the restrict qualification pessimizes IPA-CP?! Martin?
>
Well, funny thing. Without restrict, IPA-CP sees (from release_ssa dump):
void Func3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108832
--- Comment #5 from Jakub Jelinek ---
Created attachment 54481
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54481&action=edit
gcc13-pr108832.patch
Untested fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108834
--- Comment #2 from Martin Liška ---
So the module name is a string that is displayed when an ASAN error happens and
I see a discrepancy in between GCC and Clang (with LTO):
$ cat jhead.i
int x;
int *p;
int main() {
p = &x;
*(p + 1) = 123;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100295
Patrick Palka changed:
What|Removed |Added
Known to work||12.2.1, 13.0
Status|ASSIGNE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108832
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=108819
Richard Biener changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108832
--- Comment #4 from Uroš Bizjak ---
(In reply to Jakub Jelinek from comment #1)
> and so ICEs if we see the same REGNO as from in a different mode.
> I think we actually don't need most of what replace_rtx is doing, we don't
> need to simplify
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90838
--- Comment #16 from Jakub Jelinek ---
(In reply to Wilco from comment #15)
> It would make more sense to move x86 backends to CTZ_DEFINED_VALUE_AT_ZERO
> == 2 so that you always get the same result even when you don't have tzcnt.
> A conditional
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90838
--- Comment #15 from Wilco ---
(In reply to Jakub Jelinek from comment #14)
> The patch does:
> + bool zero_ok = CTZ_DEFINED_VALUE_AT_ZERO (TYPE_MODE (type), ctzval)
> == 2;
> +
> + /* Skip if there is no value defined at zero, or if we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108351
--- Comment #5 from Martin Jambor ---
If you rename main to something else, like bar, and so the calls to f
outside of the loop are not considered cold, you get the GCC 12
behavior. Is this reduced from a real-world problem?
Because on the tes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108835
Bug ID: 108835
Summary: gm2 tests at large -jNN numbers do not return
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: te
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108832
--- Comment #3 from Jakub Jelinek ---
ICEs since r13-4224-g826c22dff6455ba32 , latent before.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108832
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108833
Richard Biener changed:
What|Removed |Added
Summary|internal compiler error:|[12 Regression] internal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108834
--- Comment #1 from Richard Biener ---
But those should be all generated early? Or if not by walking DECL_CONTEXT up
to the TRANSLATION_UNIT_DECL and from its location derive the filename.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108832
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108821
Richard Biener changed:
What|Removed |Added
Summary|[11/12/13 Regression] LIM |[11/12 Regression] LIM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108821
--- Comment #4 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:4c4f0f7acd6b96ee744ef598cbea5c7046a33654
commit r13-6114-g4c4f0f7acd6b96ee744ef598cbea5c7046a33654
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108834
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108834
Bug ID: 108834
Summary: LTO: ltrans temporary file is used as module name in
ASAN
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Pri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108833
Bug ID: 108833
Summary: internal compiler error: Segmentation fault (GCC
12.1.1)
Product: gcc
Version: 12.1.1
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90838
--- Comment #14 from Jakub Jelinek ---
The patch does:
+ bool zero_ok = CTZ_DEFINED_VALUE_AT_ZERO (TYPE_MODE (type), ctzval) ==
2;
+
+ /* Skip if there is no value defined at zero, or if we can't easily
+return the correct value
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108832
Bug ID: 108832
Summary: [13 Regression] ICE in replace_rtx, at rtlanal.cc:3358
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931
--- Comment #9 from Sam James ---
For completeness, this originated from
https://github.com/Perl/perl5/issues/19776, I believe.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108831
--- Comment #2 from Uroš Bizjak ---
(In reply to Uroš Bizjak from comment #1)
> The patch also handles constant memory operands on x86_64.
--cut here--
struct S
{
unsigned char pad1;
unsigned char val;
unsigned short pad2;
};
unsigned ch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108831
Uroš Bizjak changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gcc do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108831
Bug ID: 108831
Summary: QImode binary ops with one zero-extracted argument can
be optimized
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108813
Kewen Lin changed:
What|Removed |Added
Last reconfirmed||2023-02-17
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108828
Richard Biener changed:
What|Removed |Added
Keywords||diagnostic, testsuite-fail
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108825
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108821
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108819
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
96 matches
Mail list logo
