https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99317
--- Comment #1 from Andrew Pinski ---
I dont think this is exactly a bug. The warning is a pedantic warning and with
void*, things are implicitly converted by standard c rules.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99322
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99038
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99317
--- Comment #3 from Andrew Pinski ---
Right.
basically what I am saying is:
x ? void* : char*
implies an implict conversion of the second operand to void*.
Without the cast, there is no implict conversion in standard C, that is what
the warning i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99346
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
--- Comment #1 from An
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99346
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93235
Andrew Pinski changed:
What|Removed |Added
CC||spop at gcc dot gnu.org
--- Comment #5 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99346
--- Comment #3 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #2)
> This is a dup of bug 93235.
I should note I reduced it to that bug report and looking at the
expand/optimized dumps to see it was also.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99354
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99364
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=22041
Andrew Pinski changed:
What|Removed |Added
CC||stefan at franke dot ms
--- Comment #10
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99370
--- Comment #1 from Andrew Pinski ---
The problem is since this transformation is done during optimization, it could
be done on a path that is not executed at all. This is why
-fsanitize=undefined/-fsanitize=unreachable should be used if you wan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99373
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Summary|[missed o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99217
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44262
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2021-03-04
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99384
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95453
Andrew Pinski changed:
What|Removed |Added
CC||jonathan.poelen at gmail dot
com
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95453
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97607
Andrew Pinski changed:
What|Removed |Added
CC||gabravier at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97607
Andrew Pinski changed:
What|Removed |Added
CC||mike.k at digitalcarbide dot
com
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93605
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99393
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97607
Andrew Pinski changed:
What|Removed |Added
CC||jonathan.poelen at gmail dot
com
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99396
Andrew Pinski changed:
What|Removed |Added
Component|libstdc++ |tree-optimization
Status|UNC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99396
Andrew Pinski changed:
What|Removed |Added
Summary|std::rotl and std::rotr do |std::rotl and std::rotr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99396
--- Comment #3 from Andrew Pinski ---
(In reply to cqwrteur from comment #2)
> I would like to see __builtin_cpp_rotl and __builtin_cpp_rotr to allow more
> aggressive optimizations since rotl and rotr are so important for
> cryptography.
You do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99312
--- Comment #3 from Andrew Pinski ---
(In reply to ktkachov from comment #2)
> We intend to deprecate that macro going forward as it's not a useful way for
> testing architecture features in aarch64. It made sense in the pre-Armv7-a
> days, but n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99312
--- Comment #4 from Andrew Pinski ---
ODP is one place where this is used:
https://opendataplane.github.io/odp/structodp__system__info__t.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99312
Andrew Pinski changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99410
--- Comment #1 from Andrew Pinski ---
I think this is the same as
https://sourceware.org/bugzilla/show_bug.cgi?id=27243 .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99432
Andrew Pinski changed:
What|Removed |Added
Depends on||99422
--- Comment #1 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99434
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99434
--- Comment #3 from Andrew Pinski ---
(In reply to cqwrteur from comment #2)
> (In reply to Andrew Pinski from comment #1)
> > This is just a register allocation issue dealing with mulx and TImode.
> >
> > If mulq was used instead (that is witho
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99437
Andrew Pinski changed:
What|Removed |Added
Summary|Error: immediate value out |[11 Regression] Error:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99437
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2021-03-07
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98792
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2021-03-07
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99312
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99370
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99195
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99432
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99422
Andrew Pinski changed:
What|Removed |Added
CC||italolmm2018 at outlook dot com
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99438
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99422
Andrew Pinski changed:
What|Removed |Added
CC||gerald at pfeifer dot com
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98865
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2021-03-07
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95431
--- Comment #2 from Andrew Pinski ---
Looks correct at the gimple level:
[t.c:6:3] # DEBUG BEGIN_STMT
[t.c:6:16] one.0_1 ={v} one;
[t.c:6:16] _2 = (char) one.0_1;
[t.c:6:8] a1[0] = _2;
[t.c:6:8] MEM [(char *)&a1 + 1B] = 770;
[t.c:6:8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95432
--- Comment #2 from Andrew Pinski ---
Assembly:
.loc 1 12 3 is_stmt 1 view .LVU12
.loc 1 10 8 is_stmt 0 view .LVU13
movaps %xmm0, (%rsp)
.loc 1 11 8 view .LVU14
movaps %xmm0, 32(%rsp)
.loc 1 12 13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95405
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99443
--- Comment #1 from Andrew Pinski ---
I think this is expected behavior. Aborting should not dump the coverage file
at all as it should be used for an really bad unexitable situation only.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99443
--- Comment #2 from Andrew Pinski ---
This behavior might even be documented but I have not looked yet.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99442
--- Comment #1 from Andrew Pinski ---
There is no way really to recover from a segfault in a manner that is suitable
for all programs. The developer could set a sigv handler if they want to do any
recovery from it. The library should not do it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99441
--- Comment #1 from Andrew Pinski ---
So line 27 has a short cutting conditional included, so technically it is
executed 30 times, one for each side of the &&.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99447
--- Comment #2 from Andrew Pinski ---
Looks like a stack overflow while doing gc. To me die_struct GTY could use a
recursive note added to it. That is just by looking at the backtrace.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95432
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99454
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99422
Andrew Pinski changed:
What|Removed |Added
CC||raj.khem at gmail dot com
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99443
--- Comment #4 from Andrew Pinski ---
It is not well documented though.
https://gcc.gnu.org/onlinedocs/gcc-10.2.0/gcc/Gcov-and-Optimization.html#Gcov-and-Optimization
Long-running applications can use the __gcov_reset and __gcov_dump facilities
t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99455
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99422
--- Comment #9 from Andrew Pinski ---
*** Bug 99455 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99456
Andrew Pinski changed:
What|Removed |Added
Keywords||ABI
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99457
--- Comment #1 from Andrew Pinski ---
stabs support really should be removed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99457
--- Comment #2 from Andrew Pinski ---
https://gcc.gnu.org/pipermail/gcc-patches/2017-July/479552.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99467
Andrew Pinski changed:
What|Removed |Added
Version|unknown |11.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99470
--- Comment #1 from Andrew Pinski ---
these two code are not equivalent at all due to overflows and such.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99470
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99470
--- Comment #3 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #2)
> The reason why int is not equivalent because signed integer overflow is
> undefined plus doing the math in 64bit or 32bit would cause a huge
> difference in some
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99473
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
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=99491
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99548
Andrew Pinski changed:
What|Removed |Added
Component|rtl-optimization|target
--- Comment #1 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99559
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58203
Andrew Pinski changed:
What|Removed |Added
CC||kabel at blackhole dot sk
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99579
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99608
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Component|driver
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99619
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99620
Andrew Pinski changed:
What|Removed |Added
Component|rtl-optimization|target
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99620
Andrew Pinski changed:
What|Removed |Added
Target||x86_64-linux-gnu
--- Comment #1 from And
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99621
Andrew Pinski changed:
What|Removed |Added
Summary|[5-11 REGRESSION] [bisected |[8,9,10,11 REGRESSION]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99632
--- Comment #1 from Andrew Pinski ---
The code is chopped off and does not declare the struct B.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99639
Bug ID: 99639
Summary: Duplicated constant in V2SI/V4SI
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancement
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99649
--- Comment #1 from Andrew Pinski ---
Gdb support for ilp32 has never been committed so I dont see how you are using
it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99652
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99677
--- Comment #3 from Andrew Pinski ---
I think this is a dup of bug 99456.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99689
Andrew Pinski changed:
What|Removed |Added
Component|c++ |middle-end
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99692
Andrew Pinski changed:
What|Removed |Added
Component|c++ |libstdc++
--- Comment #1 from Andrew Pin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99692
--- Comment #2 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #1)
> Right the problem is here (and not with the compiler itself if there is a
> problem):
> /home/ubuntu/upstream-gcc/include/c++/11.0.1/ostream:747:46: error: no mat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99693
--- Comment #2 from Andrew Pinski ---
Loop unswitching is correctly only turned on at -O3+. So you want to move it to
-O2. Note loop unswitching can cause performance problems due to increase of
usage of the icache and such.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99698
--- Comment #1 from Andrew Pinski ---
>AFAICT there is no way to reliably detect armv8.2-a.
There is supposed to be See PR 99312 .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99706
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.0
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99706
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2021-03-22
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99707
--- Comment #1 from Andrew Pinski ---
Gcc does not know that x will be negative.
Note: x == -1.0 is well defined. As x is converted to double from unsigned int.
-Wconversion might warn about this but I have not tried.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99707
--- Comment #2 from Andrew Pinski ---
Also this might be caught at runtime with -fsanitizer=undefined but I have not
tried yet. Since this is undefined behavior in this case unlike the original
PR93806.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99707
--- Comment #4 from Andrew Pinski ---
The front end does not normally do constant prop if the variable is not a
const/constexpr so the warning would be done in the middle end and might have
false warnings so it might not be useful.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99706
Andrew Pinski changed:
What|Removed |Added
Version|11.0|10.1.0
Summary|[11 Regression
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69549
--- Comment #6 from Andrew Pinski ---
(In reply to Thiago Macieira from comment #5)
> BTW, Clang solved this by making __seg_fs, __seg_gs macros that resolve to
> __attribute__:
> That way, they don't need to be deduced as qualifiers in C, l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99736
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29970
Andrew Pinski changed:
What|Removed |Added
CC||tunagul29 at icloud dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99779
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99784
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96956
Andrew Pinski changed:
What|Removed |Added
CC||mh+gcc at glandium dot org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99785
--- Comment #1 from Andrew Pinski ---
-O0 -ftime-report:
callgraph ipa passes : 6.16 ( 19%) 0.94 ( 20%) 7.10 ( 19%)
62M ( 6%)
(NOTE this is the trunk with checking enabled and not GCC built with
--enable-checking=release
1 - 100 of 32443 matches
Mail list logo