https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102976
--- Comment #4 from CVS Commits ---
The releases/gcc-10 branch has been updated by Peter Bergner
:
https://gcc.gnu.org/g:7729d2c96d5eac9537c78d368bbc037bea13f988
commit r10-10399-g7729d2c96d5eac9537c78d368bbc037bea13f988
Author: Peter Bergner
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104040
Bug ID: 104040
Summary: linker: when exported template class from module is
used in several .cpp with same tpl arg ~ undefined
reference to not default non-inline destructor
On 1/13/22 17:30, David Malcolm wrote:
On Thu, 2022-01-13 at 17:08 -0500, Jason Merrill wrote:
When a sequence of diagnostic messages bounces back and forth
repeatedly
between two includes, as with
#include
std::map m ("123", "456");
The output is quite a bit longer than necessary
On 1/14/22 16:49, David Malcolm wrote:
On Mon, 2021-12-13 at 09:58 -0500, Jason Merrill via Gcc-patches wrote:
On 12/13/21 06:02, Jonathan Wakely wrote:
On Sun, 12 Dec 2021 at 05:39, Jason Merrill mailto:ja...@redhat.com>> wrote:
>
> In reading C++ diagnostics, it's often hard to find the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104039
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104039
Bug ID: 104039
Summary: AArch64 Redundant instruction moving general to vector
register
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
From c2b74fd7cf2668d288f46da42565e5eb954e5e1f Mon Sep 17 00:00:00 2001
From: Thomas Rodgers
Date: Fri, 14 Jan 2022 18:30:27 -0800
Subject: [PATCH] libstdc++: Add missing free functions for atomic_flag
[PR103934]
libstdc++-v3/ChangeLog:
PR103934
* include/std/atomic: Add missing free
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59448
--- Comment #26 from Andrew Pinski ---
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0750r1.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59448
Andrew Pinski changed:
What|Removed |Added
Keywords||wrong-code
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104028
--- Comment #10 from Giulio Benetti ---
Ah, forgot to mention that it builds fine with -O0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101715
Marek Polacek changed:
What|Removed |Added
Keywords||patch
--- Comment #17 from Marek
This is a "canonical types differ for identical types" ICE, which started
with r11-4682. It's a bit tricky to explain. Consider:
template struct S {
S bar() noexcept(T::value); // #1
S foo() noexcept(T::value); // #2
};
template S S::foo() noexcept(T::value) {} // #3
We ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103782
--- Comment #6 from urbanjost at comcast dot net ---
Thanks for the quick response! Fantastic!
That gets me below a dozen bug reports. I'll have to go break something new :>
g95/gfortran saved fortran IMHO. Thanks to all the gfortran heroes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104038
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104038
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104028
--- Comment #9 from Andreas Schwab ---
It's a duplicated case vector load, where the second one is placed far off from
its table.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104031
--- Comment #6 from Sergei Trofimovich ---
> void __static_initialization_and_destruction_0 (int __initialize_p, int
> __priority)
> {
> struct InfoD.2399 D.2453 = {.arityD.2402=0};
Having poked at -fdump-tree-all-raw I now think `=
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103892
David Malcolm changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
Hi!
As reported, libgnat-12.so gets PT_GNU_STACK RWE, which means it doesn't
work in some SELinux configurations.
This is caused by the a-nbnbig.o file, which is a ghost unit and since
r12-5670 the FE emits an object file for it, but exits before compile_file
has a chance to finalize it e.g. with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104027
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:952b7dbb418198f86d7829aaf9d7f9fc7714a8b3
commit r12-6599-g952b7dbb418198f86d7829aaf9d7f9fc7714a8b3
Author: Andrew Pinski
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104029
David Malcolm changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
On Fri, 2022-01-14 at 17:53 -0500, David Malcolm wrote:
> gcc/analyzer/ChangeLog:
> PR analyzer/104029
> * sm-taint.cc (taint_state_machine::alt_get_inherited_state):
> Remove gcc_unreachable from default case for unary ops.
>
> gcc/testsuite/ChangeLog:
> PR
Hi!
C++20:
#include
auto cmp4way(double a, double b)
{
return a <=> b;
}
expands to:
ucomisd %xmm1, %xmm0
jp .L8
movl$0, %eax
jne .L8
.L2:
ret
.p2align 4,,10
.p2align 3
.L8:
comisd %xmm0, %xmm1
movl$-1,
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as cc3b67e40140ec79f86e79a96d7fdd169b84faaf.
gcc/analyzer/ChangeLog:
* sm-taint.cc (taint_state_machine::combine_states): Handle combination
of has_ub and has_lb.
gcc/testsuite/ChangeLog:
*
gcc/analyzer/ChangeLog:
PR analyzer/104029
* sm-taint.cc (taint_state_machine::alt_get_inherited_state):
Remove gcc_unreachable from default case for unary ops.
gcc/testsuite/ChangeLog:
PR analyzer/104029
* gcc.dg/analyzer/pr104029.c: New test.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104029
--- Comment #4 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:8931adfa0530590d21e74e5c7a1f8d26df575775
commit r12-6597-g8931adfa0530590d21e74e5c7a1f8d26df575775
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104031
--- Comment #5 from Sergei Trofimovich ---
gcc-11 for comparison did not seem to have `struct InfoD.2399 D.2453 =
{.arityD.2402=0};` style nodes and encoded stores explicitly:
main.cc.244t.optimized:
voidD.48 _GLOBAL__sub_I_main ()
{
struct
On Sat, 18 Sept 2021 at 05:12, Thomas Rodgers
wrote:
> From: Thomas Rodgers
>
> Let's try this one instead.
>
> Signed-off-by: Thomas Rodgers
>
If you're doing DCO "Signed-off-by" commits you don't need FSF copyright
notices in the new tests.
I no longer put any copyright notices in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85150
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
Snapshot gcc-10-20220114 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20220114/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Fri, 14 Jan 2022 at 21:49, David Malcolm wrote:
>
> Jonathan, did you try the v2 patch?
>
No, sorry.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104028
--- Comment #8 from Giulio Benetti ---
Note that bug is still present in gcc 11.2.0 so it's probable it's still in
master branch.
Thank you for taking care.
Best regards
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104028
--- Comment #7 from Giulio Benetti ---
Created attachment 52200
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52200=edit
Pre-processed sg_vpd.c(sg_vpd.s)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104028
--- Comment #6 from Giulio Benetti ---
Created attachment 52199
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52199=edit
Pre-processed sg_vpd.c(sg_vpd.i)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104028
--- Comment #5 from Giulio Benetti ---
This is the output log with -v. Now it's built not in parallel and the file
where gcc fails is not sg_dd.c so I'm going to update .i and .s files.
```
Target: m68k-buildroot-uclinux-uclibc
Configured
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104031
--- Comment #4 from Sergei Trofimovich ---
Great test, Andrew!
Something is completely dropped initialization of Info{} input argument to
s_op. As if it's lifetime ends before RegisterPrimOp{} enters:
--- main.s.good 2022-01-14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79685
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=104038
--- Comment #4 from Martin Sebor ---
The problem is reproducible with -O1 and above. To confirm it's not infinite
recursion I let the process run for about an hour before killing it. Memory
consumption seems to slowly but steadily increase as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104038
--- Comment #3 from Martin Sebor ---
The basic block being analyzed is bb 2 in clang::clangd::stdlib::initialize().
What's unusual about it is that it's a sequence of 2464 assignments like so:
:
SymCount_21 = 0;
SymCount_22 = SymCount_21 +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104037
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2022-01-14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104038
--- Comment #2 from Martin Sebor ---
Created attachment 52198
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52198=edit
Unreduced test case.
The attached translation unit reproduces the infinite loop.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104038
--- Comment #1 from Martin Sebor ---
Created attachment 52197
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52197=edit
Patch needed to trigger the infinite loop.
When the attached patch is applied the infinite loop can be triggered by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104038
Bug ID: 104038
Summary: ranger infinite loop on a PHI statement
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77667
--- Comment #5 from anlauf at gcc dot gnu.org ---
Seems fixed on mainline for gcc-12.
Most likely fix: r12-6557 for pr67804.
On Mon, 15 Nov 2021 at 08:57, Matthias Kretz wrote:
> ping. OK to push?
>
Sorry for the delay - this is OK for trunk.
> On Tuesday, 8 June 2021 14:12:23 CET Matthias Kretz wrote:
> > From: Matthias Kretz
> >
> > Explicitly support use of the stdx::simd implementation in situations
> > where
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104037
Bug ID: 104037
Summary: [12 regression] excess errors in
g++.old-deja/g++.robertl/eb43.C after r12-6581
Product: gcc
Version: 12.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104036
Bug ID: 104036
Summary: Derived type assigment to allocatable with dynamic
type
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99256
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Dear all,
this is a rather satisfying mini-patch which removes code to fix a bug.
The intrinsics MOVE_ALLOC, C_F_POINTER, and C_F_PROCPOINTER require
deferred checks of part of their actual argument types which may be of
"any" type. This however excludes alternate return specifiers which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99256
--- Comment #6 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:70e24c9682ddbcade0301665bccd8e7f928d0082
commit r12-6596-g70e24c9682ddbcade0301665bccd8e7f928d0082
Author: Harald Anlauf
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104035
Bug ID: 104035
Summary: [12 regression] g++.dg/torture/pr57993-2.C fails with
excess errors after r12-6586
Product: gcc
Version: 12.0
Status: UNCONFIRMED
> On Jan 14, 2022, at 12:58 PM, Martin Sebor wrote:
>
> On 1/14/22 11:29, Qing Zhao wrote:
>>> On Jan 14, 2022, at 12:11 PM, Martin Sebor wrote:
>>>
>>> On 1/14/22 09:30, Qing Zhao wrote:
> On Jan 14, 2022, at 6:45 AM, Richard Biener
> wrote:
>
> On Thu, Jan 13, 2022 at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103973
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
On 1/14/22 20:41, Andreas Krebbel via Gcc-patches wrote:
> On 1/14/22 08:37, Richard Biener wrote:
> ...
>> Can the gist of this bug be put into the GCC bugzilla so the rev can
>> refer to it?
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104034
>
>> Can we have a testcase even?
> The testcase
On Fri, 14 Jan 2022, 14:17 Michael Matz via Gcc, wrote:
> Hello,
>
> On Thu, 13 Jan 2022, Martin Uecker wrote:
>
> > > > > Handling all volatile accesses in the very same way would be
> > > > > possible but quite some work I don't see much value in.
> > > >
> > > > I see some value.
> > > >
> >
On Fri, Jan 14, 2022 at 11:42 AM Andreas Krebbel via Gcc-patches
wrote:
>
> On 1/14/22 08:37, Richard Biener wrote:
> ...
> > Can the gist of this bug be put into the GCC bugzilla so the rev can
> > refer to it?
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104034
>
> > Can we have a testcase
On 1/14/22 08:37, Richard Biener wrote:
...
> Can the gist of this bug be put into the GCC bugzilla so the rev can
> refer to it?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104034
> Can we have a testcase even?
The testcase from Jakub is in the BZ. However, since it doesn't fail with head
I
Excerpts from Martin Liška's message of Januar 14, 2022 4:51 pm:
> On 1/14/22 16:46, Martin Liška wrote:
>> Hello.
>>
>> I noticed that when I run:
>> ACLOCAL=~/bin/automake-1.15.1/bin/aclocal
>> AUTOMAKE=~/bin/automake-1.15.1/bin/automake autoconf
>>
>> in gcc subfolder I get the following
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101260
--- Comment #16 from Andrew Pinski ---
I wonder if makes sense to create either a RTL testcase which fails on s390
still (or did in GCC 10)?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101260
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101260
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101260
--- Comment #13 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #12)
> A patch was submitted here:
> https://gcc.gnu.org/pipermail/gcc-patches/2021-October/581172.html
Another patch was submitted here too:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101260
--- Comment #12 from Andrew Pinski ---
A patch was submitted here:
https://gcc.gnu.org/pipermail/gcc-patches/2021-October/581172.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101260
Andrew Pinski changed:
What|Removed |Added
CC||krebbel at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104034
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104034
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104005
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2022-01-14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104034
Andreas Krebbel changed:
What|Removed |Added
Last reconfirmed||2022-01-14
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104034
Bug ID: 104034
Summary: Miscompilation of LLVM on s390x with -march=z13
-mtune=z14 in GCC 8.x
Product: gcc
Version: 8.5.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104033
Bug ID: 104033
Summary: [12 regression] g++.dg/cpp0x/constexpr-compare2.C
fails with excess errors after r12-6578
Product: gcc
Version: 12.0
Status: UNCONFIRMED
On 1/14/22 11:29, Qing Zhao wrote:
On Jan 14, 2022, at 12:11 PM, Martin Sebor wrote:
On 1/14/22 09:30, Qing Zhao wrote:
On Jan 14, 2022, at 6:45 AM, Richard Biener wrote:
On Thu, Jan 13, 2022 at 2:45 AM Qing Zhao wrote:
Hi, Richard,
This is the updated version for the second patch,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104026
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
CC||rsandifo at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100952
--- Comment #15 from seurer at gcc dot gnu.org ---
Looking through test results I see that gcc.target/powerpc/pr56605.c and
gcc.target/powerpc/prefix-no-update.c are still failing today.
As noted by Tobias in the PR, the loop_vec_info constructor wasn't
initializing the new partial_load_store_bias field.
Tested on aarch64-linux-gnu and pushed as obvious.
Richard
gcc/
PR middle-end/104026
* tree-vect-loop.c (_loop_vec_info::_loop_vec_info): Initialize
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104026
--- Comment #14 from CVS Commits ---
The master branch has been updated by Richard Sandiford :
https://gcc.gnu.org/g:79ae13067f6afabcbae4784ada07dcbb7f00953e
commit r12-6594-g79ae13067f6afabcbae4784ada07dcbb7f00953e
Author: Richard Sandiford
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101022
Bill Schmidt changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100952
Bill Schmidt changed:
What|Removed |Added
CC||wschmidt at gcc dot gnu.org
--- Comment
On Thu, 13 Jan 2022 21:54:45 PST (-0800), gcc-patches@gcc.gnu.org wrote:
On Fri, Jan 14, 2022 at 4:42 AM Palmer Dabbelt wrote:
The code generated by -mcmodel=medany is defined to be
position-independent, but is not guarnteed to function correctly when
linked into position-independent
> On Jan 14, 2022, at 12:11 PM, Martin Sebor wrote:
>
> On 1/14/22 09:30, Qing Zhao wrote:
>>> On Jan 14, 2022, at 6:45 AM, Richard Biener
>>> wrote:
>>>
>>> On Thu, Jan 13, 2022 at 2:45 AM Qing Zhao wrote:
Hi, Richard,
This is the updated version for the second
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104031
--- Comment #3 from Andrew Pinski ---
Reduced testcase without any headers:
struct vector
{
vector(){} ~vector(){}
};
struct Info {
vector args;
int arity = 0;
};
struct RegisterPrimOp
{
[[gnu::noipa, gnu::noinline]]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103782
--- Comment #5 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:a4a8ae123cd70188e4b4bf5e288a84e0a76fb0fd
commit r12-6593-ga4a8ae123cd70188e4b4bf5e288a84e0a76fb0fd
Author: Harald Anlauf
Date:
When a returns_twice call has an associated abnormal edge, the edge
corresponds to the "second return" from the call. It wouldn't make sense
if any executable statements appeared between the call and the
destination of the edge (they wouldn't be re-executed upon the "second
return"), so verify
A returns_twice call may have associated abnormal edges that correspond
to the "second return" from the call. If the call is duplicated, the
copies of those edges also need to be abnormal, but e.g. tracer does not
enforce that. Just prohibit the (unlikely to be useful) duplication.
gcc/ChangeLog:
gcc/ChangeLog:
* tree-ssa-sink.c (select_best_block): Punt if selected block
has incoming abnormal edges.
gcc/testsuite/ChangeLog:
* gcc.dg/setjmp-7.c: New test.
---
gcc/testsuite/gcc.dg/setjmp-7.c | 13 +
gcc/tree-ssa-sink.c | 6 ++
2 files
> I approved the initial sink patch (maybe not clearly enough).
I wasn't entirely happy with that patch. The new version solves this better.
> Can you open
> a bugreport about the missing CFG verification and list the set of FAILs
> (all errors in some passes similar to the one you fixed in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443
Bug 88443 depends on bug 101475, which changed state.
Bug 101475 Summary: missing -Wstringop-overflow storing a compound literal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101475
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101475
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101475
--- Comment #3 from CVS Commits ---
The master branch has been updated by Martin Sebor :
https://gcc.gnu.org/g:72332337e3d8acbb21398b8d123f1bfe77a8327e
commit r12-6592-g72332337e3d8acbb21398b8d123f1bfe77a8327e
Author: Martin Sebor
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104031
--- Comment #2 from Andrew Pinski ---
I can remove std::string but not figure out how to remove std::vector yet:
#include
#include
struct string
{
string(int){}
};
struct allocator
{
allocator(){}
};
struct vector
{
vector(allocator
On 1/14/22 09:30, Qing Zhao wrote:
On Jan 14, 2022, at 6:45 AM, Richard Biener wrote:
On Thu, Jan 13, 2022 at 2:45 AM Qing Zhao wrote:
Hi, Richard,
This is the updated version for the second patch, which is mainly the change for
"Enable -Wuninitialized + -ftrivial-auto-var-init for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89069
--- Comment #3 from Antony Lewis ---
This bug is still valid as of gcc 11.2.1 20220114
15 | end module test
| 1
internal compiler error: Segmentation fault
0x160a5b7 internal_error(char const*, ...)
???:0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104012
--- Comment #6 from Martin Sebor ---
To expand a bit on the fuzziness at level 1. The logic is documented under the
-Wformat-overflow warning like so:
Numeric arguments that are known to be bounded to a subrange of their type,
or string
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100085
Bill Schmidt changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Converting the strlen/sprintf pass to Ranger has considerably
improved the accuracy of -Wformat-overflow warnings: they can avoid
triggering for safe input even at -O0 while at the same time detect
provable overflow. The conversion didn't come with any tests so in
r12-6591 I committed one that
Hi Christophe,
This patch relaxes the addressing modes for the mve full load and stores
(by full loads and stores I mean non-widening or narrowing loads and
stores resp). The code before was requiring a LO_REGNUM for these, where
this is only a requirement if the load is widening or the store
HI David,
I've been tinkering with the static analyzer for the last few days. I find
the project of adding SARIF output to the analyzer intresting. I'm writing
this to let you know that I'm trying to learn the codebase.
Thank you.
On Tue, Jan 11, 2022, 7:09 PM David Malcolm wrote:
> On Tue,
> On Jan 14, 2022, at 6:45 AM, Richard Biener
> wrote:
>
> On Thu, Jan 13, 2022 at 2:45 AM Qing Zhao wrote:
>>
>> Hi, Richard,
>>
>> This is the updated version for the second patch, which is mainly the change
>> for "Enable -Wuninitialized + -ftrivial-auto-var-init for address taken
>>
On Fri, Jan 14, 2022 at 11:14 AM Michael Matz via Gcc wrote:
>
> Hello,
>
> On Fri, 14 Jan 2022, Martin Liška wrote:
>
> > Hello.
> >
> > I'm working on a testsuite clean-up where some of the files are wrongly
> > named.
> > More precisely, so files have .cc extension and should use .C. However
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85741
Bug 85741 depends on bug 104012, which changed state.
Bug 104012 Summary: [12 regression] -Wformat-truncation warnings not taking
previous length check into account
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104012
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104012
Martin Sebor changed:
What|Removed |Added
Resolution|--- |INVALID
Blocks|
1 - 100 of 250 matches
Mail list logo
