https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103946
Jason Merrill changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103946
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:787d66eb6c53094161fb86e64ddf65f21389f63d
commit r12-6381-g787d66eb6c53094161fb86e64ddf65f21389f63d
Author: Jason Merrill
Date:
In the patch for PR92385 I added asserts to see if we tried to make a
vec_init of a vec_init, but didn't see any in regression testing. This
testcase is one case, which seems reasonable: we create a VEC_INIT_EXPR for
the aggregate initializer, and then again to express the actual
initialization
On 1/7/22 07:06, Jakub Jelinek wrote:
Hi!
The match.pd address_comparison simplification can only handle
ADDR_EXPR comparisons possibly converted to some other type (I wonder
if we shouldn't restrict it in address_compare to casts to pointer
types or pointer-sized integer types, I think we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54279
--- Comment #10 from Andrew Pinski ---
(In reply to Karlson2k from comment #9)
> (In reply to comment #8)
> > Fixed. Thanks for your report.
>
> Nice!
> Shouldn't we do the same for other tools/languages? Like ada, java?
Java has seen been
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66356
--- Comment #1 from Andrew Pinski ---
This is what I have for a cross compiler (I have not tested building natively
this way really):
lrwxrwxrwx 1 apinski apinski 20 Oct 26 2019 bfd -> ../gits/binutils/bfd
lrwxrwxrwx 1 apinski apinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103942
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |10.4
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103944
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103947
Andrew Pinski changed:
What|Removed |Added
Blocks||87403
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57632
--- Comment #7 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #6)
> Reduced testcase for that:
> void f(void);
> void f(void) throw(int);
> void f(void) throw(int);
>
> Noexcept has the same issue:
> void g(void);
> void g(void)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100588
--- Comment #1 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:75047f79550fd10a8f86f5c72deab10cde77
commit r12-6380-g75047f79550fd10a8f86f5c72deab10cde77
Author: Jason Merrill
Date:
The standard says that a destroying operator delete is preferred, but that
only applies to the delete-expression, not the cleanup if a new-expression
initialization throws. As a result of this patch, several of the destroying
delete tests don't get EH cleanups, but I'm turning off the warning in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94061
Frank Heckenbach changed:
What|Removed |Added
CC||f.heckenb...@fh-soft.de
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103947
Bug ID: 103947
Summary: wishlist: warning if explicitly defaulted (spaceship)
operator is deleted
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103940
--- Comment #2 from Martin Sebor ---
It makes sense to me, David.
This patch provides new tests for the core language and compiler
dependent library changes proposed in WG14 N2653 [1] for C2x.
Tested on Linux x86_64.
gcc/testsuite/ChangeLog:
2021-05-31 Tom Honermann
* gcc.dg/atomic/c2x-stdatomic-lockfree-char8_t.c: New test.
*
This patch implements the core language and compiler dependent library
changes proposed in WG14 N2653 [1] for C2x. The changes include:
- Change of type for UTF-8 string literals from array of char to array
of char8_t (unsigned char) when targeting C2x.
- A new atomic_char8_t typedef.
- A new
This series of patches implements the core language features for the
WG14 N2653 [1] proposal to provide char8_t support in C. These changes
are intended to align char8_t support in C with the support provided in
C++20 via WG21 P0482R6 [2].
These patches addresses feedback provided in response
This patch completes implementation of the C++20 proposal P0482R6 [1] by
adding declarations of std::c8rtomb() and std::mbrtoc8() in if
provided by the C library in .
This patch addresses feedback provided in response to a previous patch
submission [2].
Autoconf changes determine if the C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102935
Michael Meissner changed:
What|Removed |Added
Attachment #52143|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102935
--- Comment #2 from Michael Meissner ---
Created attachment 52143
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52143=edit
Patch to update code generation test
The test wants to load all 1's into a vector register. On power8 it uses
Fix pr101384-1.c code generation test.
Add support for the compiler using XXSPLTIB reg,255 to load all 1's into a
register on power9 and above instead of using VSPLTI{B,H,W} reg,-1.
gcc/testsuite/
2022-01-07 Michael Meissner
PR testsuite/102935
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103910
--- Comment #11 from Sam James ---
(In reply to Andrew Pinski from comment #10)
> Someone would have hit this a long time ago, in GCC 4.3.0 or latter.
My point was that some software has recently started building with PCH by
default and hence
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as 11a2ff8d981110e1562caf7d98e41c1ff2e76056.
gcc/analyzer/ChangeLog:
* engine.cc (impl_run_checkers): Pass logger to engine ctor.
* region-model-manager.cc
PR analyzer/103546 seems to involve an issue in how the analyzer
tracks which decls have escaped, so this patch adds a way to directly
test this from DejaGnu.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r12-6377-g4409152a4acaec5b58a93996088d0df9aaa779b8.
This patch adds a debug function that I've found handy when debugging
a problem with handling the decl yy_buffer_stack" in PR analyzer/103546.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r12-6376-gc1b7d28a5987e74232b7f054849f8bd8ccc7e7de.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103546
--- Comment #5 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:4409152a4acaec5b58a93996088d0df9aaa779b8
commit r12-6377-g4409152a4acaec5b58a93996088d0df9aaa779b8
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103546
--- Comment #4 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:c1b7d28a5987e74232b7f054849f8bd8ccc7e7de
commit r12-6376-gc1b7d28a5987e74232b7f054849f8bd8ccc7e7de
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57632
--- Comment #6 from Andrew Pinski ---
(In reply to Jonathan Wakely from comment #5)
> I agree with comment 3 that the current diagnostic is poor:
Oh I missed that.
>
> #include
> void* operator new(std::size_t mem) throw(std::bad_alloc);
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103946
--- Comment #3 from Andrew Pinski ---
Confirmed reduced further:
struct s1 { s1(); };
class s2 { s1 f1[2]{}; };
s2 a;
CUT ---
This was most likely caused by one of Jason's recent patches that should have
improved this case.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103946
Jakub Jelinek changed:
What|Removed |Added
Keywords||needs-reduction
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102935
Michael Meissner changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103538
Eric Botcazou changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103946
--- Comment #1 from David Binderman ---
Reduced C++ code is:
class UnicodeSet {
virtual UnicodeSet complement();
};
enum { URX_GC_T, URX_LAST_SET };
class RegexStaticSets {
RegexStaticSets();
UnicodeSet fPropSets[URX_LAST_SET]{};
};
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102692
David Malcolm changed:
What|Removed |Added
Last reconfirmed||2022-01-07
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103910
--- Comment #10 from Andrew Pinski ---
(In reply to Sam James from comment #8)
> More people than I expected hit this downstream in Gentoo. Your commit seems
> to apply cleanly and work on top of the 11 branch. Could somebody apply it
> if
Snapshot gcc-10-20220107 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20220107/
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 Jan 5, 2022, at 10:59 AM, Qing Zhao via Gcc-patches
> wrote:
>
> Hi, Richard,
>
> Thanks a lot for the review and questions.
> See my reply embedded below:
>
>
>> On Jan 5, 2022, at 4:33 AM, Richard Biener
>> wrote:
>>
>> On Thu, Dec 16, 2021 at 5:00 PM Qing Zhao wrote:
>>>
>>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103943
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103943
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103946
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103946
Bug ID: 103946
Summary: ice in build_vec_init_expr, at cp/tree.c:791
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20040
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:6cd51207f5732b5258e883e9030b94c987b6d696
commit r12-6375-g6cd51207f5732b5258e883e9030b94c987b6d696
Author: Jason Merrill
Date:
Apparently we need to check the accessibility of the deallocation function
even if there is no initialization.
Tested x86_64-pc-linux-gnu, applying to trunk.
PR c++/20040
gcc/cp/ChangeLog:
* init.c (build_new_1): Also build pointer cleanup if
TYPE_GETS_DELETE.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102941
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102941
--- Comment #9 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:997130f778c56466a825627644e510960585521b
commit r12-6374-g997130f778c56466a825627644e510960585521b
Author: Andrew Pinski
Date:
> On Jan 7, 2022, at 4:06 PM, Iain Sandoe wrote:
>
> Hi Folks,
>
> In the aarch64 Darwin ABI we have an unusual (OK, several unusual) feature of
> the calling convention.
>
> When an argument is passed *in a register* and it is integral and less than
> SI it is promoted (with appropriate
On Fri, Jan 07, 2022 at 10:40:50PM +0100, Thomas Koenig wrote:
> One thing that one has to watch out for is a big-endian IBM long double
> file, so the byte swapping will have to be done before assigning
> the value.
I've tried to handle that right, i.e. on unformatted read with
byte-swapping and
On 07.01.22 20:52, Jakub Jelinek wrote:
Here is completely untested patch that implements something,
but doesn't implement the gcc option stuff, nor the CONVERT=
syntax to supply multiple conversion options nor done anything
about env var nor any testcases.
But it tries to have the
Hi Jakub,
So, the following patch adds -fbuilding-libgfortran option and uses
it together with TARGET_GLIBC_M* checks to decide whether to use
libquadmath APIs (for the IEEE quad kind=16 if -fbuilding-libgfortran
and not glibc or glibc is older than 2.32) or glibc 2.32 APIs
(otherwise). This
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103763
--- Comment #1 from Michael Meissner ---
Created attachment 52141
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52141=edit
Patch to fix the insn count
Update the insn regex for power10.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103763
Michael Meissner changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
Hi Folks,
In the aarch64 Darwin ABI we have an unusual (OK, several unusual) feature of
the calling convention.
When an argument is passed *in a register* and it is integral and less than SI
it is promoted (with appropriate signedness) to SI. This applies when the
function parm is named
Fix fold-vec-splat-floatdouble testsuite failure on power10
When I added support for generating XXSPLTIDP on December 15th, 2021, I
missed updating the fold-vec-splat-floatdouble.c test to add to the regex
for the instructions generated. This patch fixes that.
gcc/testsuite/
2022-01-07 Michael
Hi Paul,
Am 07.01.22 um 14:42 schrieb Paul Richard Thomas via Fortran:
I doubt that this is a regression on 9-11 branches since the testcase
compiles correctly on each of my copies of these branches. IMHO it is
rather more likely to have been caused by
64f9623765da3306b0ab6a47997dc5d62c2ea261,
On Fri, Jan 7, 2022 at 3:57 PM Paul A. Clarke wrote:
>
> On Fri, Jan 07, 2022 at 02:40:51PM -0500, David Edelsohn via Gcc-patches
> wrote:
> > +#ifdef __LITTLE_ENDIAN__
> > + /* Sum across four integers with two integer results. */
> > + asm ("vsum2sws %0,%1,%2" : "=v" (result) : "v" (vsum),
On Fri, Jan 07, 2022 at 02:40:51PM -0500, David Edelsohn via Gcc-patches wrote:
> +#ifdef __LITTLE_ENDIAN__
> + /* Sum across four integers with two integer results. */
> + asm ("vsum2sws %0,%1,%2" : "=v" (result) : "v" (vsum), "v" (zero));
> + /* Note: vec_sum2s could be used here, but on
On Fri, Jan 7, 2022 at 3:35 PM Paul A. Clarke wrote:
>
> On Fri, Jan 07, 2022 at 02:23:14PM -0500, David Edelsohn wrote:
> > > Power10 ISA added `vextract*` instructions which are realized in the
> > > `vec_extractm` instrinsic.
> > >
> > > Use `vec_extractm` for `_mm_movemask_ps`,
On Fri, Jan 7, 2022 at 3:32 PM Paul A. Clarke wrote:
>
> On Fri, Jan 07, 2022 at 02:15:22PM -0500, David Edelsohn wrote:
> > > Power10 ISA added `xxblendv*` instructions which are realized in the
> > > `vec_blendv` instrinsic.
> > >
> > > Use `vec_blendv` for `_mm_blendv_epi8`, `_mm_blendv_ps`,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65253
David Binderman changed:
What|Removed |Added
CC||dcb314 at hotmail dot com
--- Comment
On Fri, Jan 07, 2022 at 02:23:14PM -0500, David Edelsohn wrote:
> > Power10 ISA added `vextract*` instructions which are realized in the
> > `vec_extractm` instrinsic.
> >
> > Use `vec_extractm` for `_mm_movemask_ps`, `_mm_movemask_pd`, and
> > `_mm_movemask_epi8` compatibility intrinsics, when
On Fri, Jan 07, 2022 at 02:15:22PM -0500, David Edelsohn wrote:
> > Power10 ISA added `xxblendv*` instructions which are realized in the
> > `vec_blendv` instrinsic.
> >
> > Use `vec_blendv` for `_mm_blendv_epi8`, `_mm_blendv_ps`, and
> > `_mm_blendv_pd` compatibility intrinsics, when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68138
Patrick Palka changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
On 1/7/22 21:14, cert+donotreply--- via Gcc wrote:
Topic 2: There's no such thing as free software, or, how to invest in OSS
security.
Wasn't this Cygnus motto: "We make free software affordable ?"
Kind regards,
--
Toon Moene - e-mail: t...@moene.org - phone: +31 346 214290
Saturnushof 14,
We invite you to join us for the CERT Vendor Meeting 2022. This will be a
virtual event, 2022-02-07 10:00-14:30 EST, via Zoom Webinar.
We'll be discussing two topics in some depth, using an extended panel format
(short presentations, moderated discussion, open discussion).
Topic 1: Log4j, a
On Fri, 7 Jan 2022, Daniil Stas via Gcc-patches wrote:
> > > @@ -4248,7 +4248,7 @@ check_format_types (const substring_loc
> > > _loc, && (!pedantic || i < 2)
> > > && char_type_flag)
> > > continue;
> > > - if (types->scalar_identity_flag
> > > + if ((types->scalar_identity_flag
On Fri, Jan 07, 2022 at 11:26:15AM +0100, Thomas Koenig wrote:
> In
>
> https://gcc.gnu.org/pipermail/fortran/2021-October/056895.html
>
> I made a suggestion how how the format could look like. I used
> a plus sign instead of a comma because I thought the environment
> variable should follow
Add sse2 isa attribute where needed and remove where not needed.
2022-01-07 Uroš Bizjak
gcc/ChangeLog:
* config/i386/mmx.md (*move_internal): Add isa attribute.
(*movv2qi_internal): Remve sse2 requirement for alternatives 4,5.
Bootstrapped and regression tested on x86_64-linux-gnu
+#ifdef __LITTLE_ENDIAN__
+ /* Sum across four integers with two integer results. */
+ asm ("vsum2sws %0,%1,%2" : "=v" (result) : "v" (vsum), "v" (zero));
+ /* Note: vec_sum2s could be used here, but on little-endian, vector
+ shifts are added that are not needed for this use-case.
+ A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69701
Language Lawyer changed:
What|Removed |Added
CC||language.lawyer at gmail dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81045
Patrick Palka changed:
What|Removed |Added
CC||jporterbugs at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65308
Patrick Palka changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
> Power10 ISA added `vextract*` instructions which are realized in the
> `vec_extractm` instrinsic.
>
> Use `vec_extractm` for `_mm_movemask_ps`, `_mm_movemask_pd`, and
> `_mm_movemask_epi8` compatibility intrinsics, when `_ARCH_PWR10`.
>
> 2021-10-21 Paul A. Clarke
>
> gcc
> *
> Power10 ISA added `xxblendv*` instructions which are realized in the
> `vec_blendv` instrinsic.
>
> Use `vec_blendv` for `_mm_blendv_epi8`, `_mm_blendv_ps`, and
> `_mm_blendv_pd` compatibility intrinsics, when `_ARCH_PWR10`.
>
> Also, copy a test from i386 for testing `_mm_blendv_ps`.
> This
Thanks for the help, that's exactly it!
Andras
On Thu, 2022-01-06 at 20:25 -0800, Andrew Pinski wrote:
> On Thu, Jan 6, 2022 at 8:13 PM Andras Tantos > wrote:
> > Hello!
> >
> > My name is Andras Tantos and I just joined this list, so if I'm
> > asking
> > something off-topic or not following
On Fri, Jan 07, 2022 at 03:33:54PM -0300, Alexandre Oliva via Gcc wrote:
> On Jan 7, 2022, Martin Jambor wrote:
>
> > Would anyone be terribly against mass renaming all *.c files (that are
> > actually C++ files) within the gcc subdirectory to ones with .cc suffix?
>
> I wouldn't mind that.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103939
--- Comment #11 from David Binderman ---
(In reply to Jonathan Wakely from comment #9)
> The fedora package has:
>
> dvdisaster-0.79.5/read-linear.c: memset(rc, sizeof(read_closure), 0xff);
>
> The chance of false positives still seems
On Jan 7, 2022, Martin Jambor wrote:
> Would anyone be terribly against mass renaming all *.c files (that are
> actually C++ files) within the gcc subdirectory to ones with .cc suffix?
I wouldn't mind that.
> (Any important caveats I might have missed?)
Having recently renamed a .c source to
Mingw32 targets use ms_printf format for printf, but mingw-w64 when
configured for UCRT uses gnu_format (via stdio.h). GCC then checks both
formats, which means that one cannot print a 64-bit integer without a
warning.
All these lines issue a warning:
printf("Hello %"PRIu64"\n", x); // 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103945
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103945
--- Comment #2 from Jonathan Wakely ---
Confirmed. This seems to be new in Clang 13 (and enabled by default, even
without -Wall). Clang 12 doesn't warn.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103945
Marek Polacek changed:
What|Removed |Added
Ever confirmed|0 |1
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103939
--- Comment #10 from Andreas Schwab ---
If the second argument matches the size of the dereferenced first argument, the
probability of a false positive should be quite small.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103942
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Build||2022-01-07 0:00
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103945
Bug ID: 103945
Summary: No warning for ordered comparison of function pointers
?
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103939
--- Comment #9 from Jonathan Wakely ---
The fedora package has:
dvdisaster-0.79.5/read-linear.c: memset(rc, sizeof(read_closure), 0xff);
The chance of false positives still seems pretty small to me.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100551
--- Comment #9 from CVS Commits ---
The releases/gcc-10 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:6a3018a4064b39a418d95c32e45fe7d6ad17ebf3
commit r10-10384-g6a3018a4064b39a418d95c32e45fe7d6ad17ebf3
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103942
--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to Martin Liška from comment #2)
> Started with r11-6928-g4225af228b5d52e8 and was fixed on master with
> r12-1005-gfe03f4fc9548b3fd.
Backporting r12-1005 (see pr100551) fixes the
On Thu, 2022-01-06 at 17:20 +0100, Martin Jambor wrote:
> Hello,
>
> another year is upon us and Google has announced there will be again
> Google Summer of Code 2022 (though AFAIK there is no specific timeline
> yet). I'd like to volunteer to be the main Org Admin for GCC again so
> let me know
On 12/7/21 15:19, Andrew MacLeod wrote:
The following patch is a slight rework of the 2 patches which flatten
rangers call stack. It needed some tweaking since some of the
routines have changed name or been adjusted.
This has been bootstrapped on x86_64-pc-linux-gnu with no
regressions. OK
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103939
--- Comment #8 from Jakub Jelinek ---
memset (whatever, sizeof(whatever), 0);
is a common mistake, that is why gcc has a warning for it too.
But your report is the first one to suggest that even other variants
happen in real-world. The thing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101901
Christopher Head changed:
What|Removed |Added
CC||headch at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103939
--- Comment #7 from Jonathan Wakely ---
I see no such usage in dvdisaster, so I assume you were talking about the
original example you gave in comment 0. Nobody is disputing the usefulness of
that warning. I was questioning whether we need to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103939
--- Comment #6 from Jonathan Wakely ---
I was replying to comment 2: "What if both the second and third arguments are
'sizeof' expressions?"
Are you saying Fedora has code doing memset(ps, sizeof(a), sizeof(b)) ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103465
--- Comment #28 from Tomas Kalibera ---
I've also tested the patch with GCC 10.3 (with several backports from gcc10
branch plus some minor fixes,
On Fri, 7 Jan 2022 at 16:00, David Malcolm wrote:
> Presumably the generated files should also change from .c to .cc (e.g.
> gengtype generates a gtype-desc.c which is actually C++).
We could do that separately (and right away), couldn't we? That could
even have been done back in the subversion
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103436
Eric Botcazou changed:
What|Removed |Added
Last reconfirmed||2022-01-07
CC|
On Thu, Nov 18, 2021 at 08:25:35PM -0600, Paul A. Clarke via Gcc-patches wrote:
> On Mon, Nov 08, 2021 at 11:42:27AM -0600, Paul A. Clarke via Gcc-patches
> wrote:
> > Gentle ping...
>
> Gentle re-ping.
Gentle re-re-ping.
> > On Wed, Oct 20, 2021 at 08:42:07PM -0500, Paul A. Clarke via
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103546
--- Comment #3 from David Malcolm ---
The -Wanalyzer-null-dereference false positive seems to be due to the analyzer
being overzealous about escaping, where it erroneously is treating
yy_buffer_stack as having escaped, and thus can be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103944
--- Comment #1 from Jakub Jelinek ---
Looking at the testcase, in fork child from a multi-threaded process only async
signal safe functions can be called until it execs, are you sure nothing else
is called?
1 - 100 of 215 matches
Mail list logo
