https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107532
Bug ID: 107532
Summary: [13 Regression] -Werror=dangling-reference false
positives in libcamera-0.0.1
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107531
--- Comment #2 from nightstrike ---
It looks like you're right. The root cause of the problem is that in my
non-reduced case, I didn't have a copy constructor, but I had a non-default
destructor that was releasing resources twice. So it's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107531
--- Comment #1 from Andrew Pinski ---
My bet is on a copy constructor being invoked.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107531
Bug ID: 107531
Summary: List of references calls destructors, add warning?
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107528
Jiang An changed:
What|Removed |Added
CC||de34 at live dot cn
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61759
--- Comment #12 from Sergey Fedorov ---
(In reply to Andrew Pinski from comment #11)
> *** Bug 107530 has been marked as a duplicate of this bug. ***
I.e. gcc12 has the same bug too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107530
--- Comment #2 from Sergey Fedorov ---
(In reply to Andrew Pinski from comment #1)
> Dup of bug 61759
>
> *** This bug has been marked as a duplicate of bug 61759 ***
I guess then it is worth adding gcc12 to confirmed to fail list there.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107530
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61759
Andrew Pinski changed:
What|Removed |Added
CC||vital.had at gmail dot com
--- Comment
On Fri, 2022-11-04 at 13:06 -0400, Jason Merrill wrote:
> On 11/4/22 11:16, David Malcolm wrote:
> > On Fri, 2022-11-04 at 10:27 -0400, Jason Merrill wrote:
> > > On 11/3/22 19:06, David Malcolm wrote:
> > > > On Thu, 2022-11-03 at 15:59 -0400, Jason Merrill via Gcc-
> > > > patches
> > > > wrote:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107530
Bug ID: 107530
Summary: ICE: in objc_eh_runtime_type, at
objc/objc-next-runtime-abi-01.cc:2795
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity:
On Fri, 2022-11-04 at 17:05 -0400, Lewis Hyatt wrote:
> [PATCH 5a/6] diagnostics: Handle generated data locations in
> edit_context
>
> Class edit_context handles outputting fixit hints in diff form that
> could be
> manually or automatically applied by the user. This will not make
> sense for
>
On Fri, 2022-11-04 at 17:05 -0400, Lewis Hyatt wrote:
> [PATCH 5b/6] diagnostics: Remove null-termination requirement for
> json::string
>
> json::string currently handles null-terminated data and so can't work
> with
> data that may contain embedded null bytes or that is not null-
> terminated.
On Saturday 05 November 2022 01:57:49 Pali Rohár wrote:
> On Monday 31 October 2022 10:55:59 Jan Beulich wrote:
> > On 30.10.2022 02:06, Pali Rohár via Binutils wrote:
> > > * GCC or LD (not sure who) sets memory alignment characteristics
> > > (IMAGE_SCN_ALIGN_MASK) into the sections of PE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53135
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment #19
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107529
Bug ID: 107529
Summary: constexpr evaluator doesn't check for destroyed
objects
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
On Monday 31 October 2022 10:55:59 Jan Beulich wrote:
> On 30.10.2022 02:06, Pali Rohár via Binutils wrote:
> > * GCC or LD (not sure who) sets memory alignment characteristics
> > (IMAGE_SCN_ALIGN_MASK) into the sections of PE executable binary.
> > These characteristics should be only in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107528
Bug ID: 107528
Summary: constexpr evaluator doesn't check for deallocate of
mismatched size
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
On 11/4/22 17:38, Vineet Gupta wrote:
commit 666fdc46bc848984ee7d2906f2dfe10e1ee5d535
Author: Jim Wilson
Date: Sat Jun 30 21:52:01 2018 +
RISC-V: Add patterns to convert AND mask to two shifts.
gcc/
* config/riscv/predicates.md (p2m1_shift_operand): New.
On 11/4/22 16:13, Jeff Law wrote:
On 11/4/22 16:59, Vineet Gupta wrote:
Hi Jakub,
I had a question about the aforementioned commit in RV backend.
(define_split
[(set (match_operand:GPR 0 "register_operand")
(and:GPR (match_operand:GPR 1 "register_operand")
On 11/4/22 16:59, Vineet Gupta wrote:
Hi Jakub,
I had a question about the aforementioned commit in RV backend.
(define_split
[(set (match_operand:GPR 0 "register_operand")
(and:GPR (match_operand:GPR 1 "register_operand")
(match_operand:GPR 2 "p2m1_shift_operand")))
+
Alexander,
I had missed your comment until now.
On Tue, 6 Sept 2022 at 13:39, Alexander Monakov wrote:
>
> On Mon, 5 Sep 2022, Philipp Tomsich wrote:
>
> > +riscv_mode_rep_extended (scalar_int_mode mode, scalar_int_mode
mode_rep)
> > +{
> > + /* On 64-bit targets, SImode register values are
Hi Jakub,
I had a question about the aforementioned commit in RV backend.
(define_split
[(set (match_operand:GPR 0 "register_operand")
(and:GPR (match_operand:GPR 1 "register_operand")
(match_operand:GPR 2 "p2m1_shift_operand")))
+ (clobber (match_operand:GPR 3
Snapshot gcc-11-20221104 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20221104/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #11 from Carlos E ---
Created attachment 53829
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53829=edit
preprocessed file on 10.2
preprocessed with echo '#include ' | gcc -x c - -E
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101491
John Hein changed:
What|Removed |Added
Attachment #53828|install libgccjit*.h under |install libgccjit*.h under
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107527
--- Comment #1 from Andrew Pinski ---
I thought I had saw this one before. Specifically something related to Darwin.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107527
Bug ID: 107527
Summary: warning: declaration of ‘void operator delete(void*,
std::size_t)’ has a different exception specifier
[-Wsystem-headers]
Product: gcc
On Fri, Nov 04, 2022 at 12:42:29PM -0400, David Malcolm wrote:
> On Fri, 2022-11-04 at 09:44 -0400, Lewis Hyatt via Gcc-patches wrote:
> > Add awareness that diagnostic locations may be in generated buffers
> > rather
> > than an actual file to other places in the diagnostics code that may
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100523
Ramana Radhakrishnan changed:
What|Removed |Added
CC||ramana at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107500
--- Comment #24 from R. Diez ---
In case somebody else wants to patch their GCC 12.2, here is the
slightly-modified patch for convenience:
https://github.com/rdiez/DebugDue/blob/master/Toolchain/Patches/Gcc12EhGlobalsAtexit.patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107466
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2022-11-04
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94604
Ramana Radhakrishnan changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101491
--- Comment #10 from John Hein ---
(In reply to John Hein from comment #9)
Oops. s/libgccgit/libgccjit/ in the previous comment.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101491
John Hein changed:
What|Removed |Added
CC||rv4chsst7e at liamekaens dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61593
--- Comment #13 from Jonathan Wakely ---
(In reply to Eric Gallager from comment #5)
> It should be pretty easy; in config/darwin.h #pragma mark is registered as
> part of the DARWIN_REGISTER_TARGET_PRAGMAS() macro like this:
>
> if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53135
--- Comment #18 from Ramana Radhakrishnan ---
Since the fix got installed in 2012 this really should have been fixed from
4.8.0 onwards.
Should we really keep this still open or can we close this out ?
Ramana
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55157
Aldy Hernandez changed:
What|Removed |Added
Attachment #53826|0 |1
is obsolete|
On Fri, Nov 04, 2022 at 08:14:23PM +0100, Jakub Jelinek via Gcc-patches wrote:
> One thing that is clear is that real_isdenormal is never true for these
> (but then a question is if flush_denormals_to_zero actually works).
So, after some more investigation, I think that is actually the case,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55157
--- Comment #10 from Aldy Hernandez ---
Original TYPE_UNSIGNED patch with leading / trailing suggestions: -2.52%
As attached: -3.62%
Moving the code out of set_range_from_nonzero_bits back into set_nonzero_bits:
-3.7%
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55157
--- Comment #9 from Aldy Hernandez ---
(In reply to Aldy Hernandez from comment #7)
> (In reply to Andrew Macleod from comment #6)
> > (In reply to Aldy Hernandez from comment #4)
> > 3) It also seems to me that you then only need to add the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107523
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-bisection
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106644
Jason Merrill changed:
What|Removed |Added
Last reconfirmed||2022-11-04
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24537
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #8 from Jonathan
On Mon, Oct 17, 2022 at 08:21:01AM +0200, Aldy Hernandez wrote:
> +// Set VALUE to its next real value, or INF if the operation overflows.
> +
> +inline void
> +frange_nextafter (enum machine_mode mode,
> + REAL_VALUE_TYPE ,
> + const REAL_VALUE_TYPE )
> +{
> + const
On 10/27/22 13:30, Lewis Hyatt wrote:
Hello-
May I please ask for a review of this patch from June? I realize it's a
10-year-old PR that doesn't seem to be bothering people much, but I still feel
like it's an unfortunate gap in C++11 support that is not hard to fix.
Original submission is
* Patrick Palka:
> On Fri, 4 Nov 2022, Florian Weimer wrote:
>
>> * Patrick Palka via Gcc-patches:
>>
>> > This patch moves the global object for constructing the standard streams
>> > out from and into the compiled library on targets that support
>> > the init_priority attribute. This means
On Fri, 4 Nov 2022, Florian Weimer wrote:
> * Patrick Palka via Gcc-patches:
>
> > This patch moves the global object for constructing the standard streams
> > out from and into the compiled library on targets that support
> > the init_priority attribute. This means that no longer
> >
Sorry for the delay, just been reminded I still had this patch
outstanding from last stage 1. Hopefully since it has been mostly
reviewed it could go in for this stage 1?
I addressed the comments and gave the slp-part of vectorizable_call some
TLC to make it work.
I also changed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98940
Bug 98940 depends on bug 102614, which changed state.
Bug 102614 Summary: [C++23] P2314R4 - Character sets and encodings
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102614
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102614
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107413
Wilco changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
e5c15eb183f17e806ad6b58c9497321ded87866f introduced a regression as
some ada tests end up passing NULL as the filename to remap_filename().
Handle this as before to fix the tests.
gcc/ChangeLog:
* file-prefix-map.cc (remap_filename): Handle NULL filenames.
Signed-off-by: Richard Purdie
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56958
serpent7776 at gmail dot com changed:
What|Removed |Added
CC||serpent7776 at gmail dot
On Fri, 2022-11-04 at 10:12 +0100, Eric Botcazou wrote:
> > gcc/ChangeLog:
> >
> > * file-prefix-map.cc (remap_filename): Allow remapping of
> > relative paths
>
> Small regression in Ada though, probably a missing guard somewhere:
>
> === gnat tests ===
>
>
> Running
On 11/4/22 05:14, Jakub Jelinek wrote:
Hi!
I've read the paper and I believe we just implement it with no changes
needed (at least since PR67224 and similar libcpp changes in GCC 10),
but I could be wrong.
The following patch at least adds a testcase from the start of the paper.
Committed as trivial fix.
gcc/testsuite/
* gcc.target/aarch64/mgeneral-regs_3.c: Fix testcase.
---
diff --git a/gcc/testsuite/gcc.target/aarch64/mgeneral-regs_3.c
b/gcc/testsuite/gcc.target/aarch64/mgeneral-regs_3.c
index
On 11/4/22 11:16, David Malcolm wrote:
On Fri, 2022-11-04 at 10:27 -0400, Jason Merrill wrote:
On 11/3/22 19:06, David Malcolm wrote:
On Thu, 2022-11-03 at 15:59 -0400, Jason Merrill via Gcc-patches
wrote:
[...snip...]
Do you have test coverage for this from the DejaGnu side? If not,
* Patrick Palka via Gcc-patches:
> This patch moves the global object for constructing the standard streams
> out from and into the compiled library on targets that support
> the init_priority attribute. This means that no longer
> introduces a separate global constructor in each TU that
On Fri, 4 Nov 2022 at 16:31, Patrick Palka wrote:
>
> On Fri, 4 Nov 2022, Jonathan Wakely wrote:
>
> > On Fri, 4 Nov 2022 at 15:08, Patrick Palka via Libstdc++
> > wrote:
> > >
> > > This patch moves the global object for constructing the standard streams
> > > out from and into the compiled
On Fri, 2022-11-04 at 09:44 -0400, Lewis Hyatt via Gcc-patches wrote:
> Add awareness that diagnostic locations may be in generated buffers
> rather
> than an actual file to other places in the diagnostics code that may
> care,
> most notably SARIF output (which needs to obtain its own snapshots
On Thu, 3 Nov 2022 23:23:55 +0100
Bernhard Reutner-Fischer wrote:
> Hi!
>
> I encounter a problem/pilot error when using the target_clones
> attribute.
>
> The symptom is that the default clone is not renamed in the output and
> thus conflicts with the (proper) global name which is used for
On Fri, 4 Nov 2022, Jonathan Wakely wrote:
> On Fri, 4 Nov 2022 at 15:08, Patrick Palka via Libstdc++
> wrote:
> >
> > This patch moves the global object for constructing the standard streams
> > out from and into the compiled library on targets that support
> > the init_priority attribute.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107525
--- Comment #9 from Giuseppe D'Angelo ---
(In reply to Jonathan Wakely from comment #5)
> Please don't! At least not in the next 9 days. We intend to vote out LFTSv3
> at next week's meeting, there will be no more proposals for LFTS
On 11/4/22 11:05, Patrick Palka wrote:
Currently __has_attribute(init_priority) always returns true, even on
targets that don't actually support init priorities, and when using
the attribute on such targets, we issue a hard error that init
priorities are unsupported. This makes it impossible to
On Fri, 2022-11-04 at 09:44 -0400, Lewis Hyatt via Gcc-patches wrote:
> The string "" is hard-coded in several places throughout
> the
> diagnostics code, and in some of those places, it is used incorrectly
> with
> respect to internationalization. (Comparing a translated string to an
>
On Fri, 2022-11-04 at 09:44 -0400, Lewis Hyatt via Gcc-patches wrote:
> The result of linemap_resolve_location() can be an ad-hoc location,
> if that is
> what was stored in a relevant macro map.
> maybe_unwind_expanded_macro_loc()
> did not previously handle this case, causing it to print the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55157
--- Comment #8 from Aldy Hernandez ---
Created attachment 53826
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53826=edit
untested
Here's what I tested and we're still around a 3% degradation for VRP.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55157
--- Comment #7 from Aldy Hernandez ---
(In reply to Andrew Macleod from comment #6)
> (In reply to Aldy Hernandez from comment #4)
>
> >
> > The patch below does this, but it does have a 3% penalty for VRP (though no
> > penalty to overall
On Fri, 4 Nov 2022 at 15:08, Patrick Palka via Libstdc++
wrote:
>
> This patch moves the global object for constructing the standard streams
> out from and into the compiled library on targets that support
> the init_priority attribute. This means that no longer
> introduces a separate global
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107526
--- Comment #1 from Geoffrey ---
And if i compile this case with gcc 11.3, it does not report NPD warning.
https://godbolt.org/z/v88PWvs3s
seems like a regression problem.
On Fri, 2022-11-04 at 10:27 -0400, Jason Merrill wrote:
> On 11/3/22 19:06, David Malcolm wrote:
> > On Thu, 2022-11-03 at 15:59 -0400, Jason Merrill via Gcc-patches
> > wrote:
[...snip...]
> >
> >
> > Do you have test coverage for this from the DejaGnu side? If not,
> > you
> > could add
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107525
Ville Voutilainen changed:
What|Removed |Added
CC||ville.voutilainen at gmail dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107526
Bug ID: 107526
Summary: - -Wanayzer-null-dereference false positive with
different behaviors when delete unrelated statement
“int *e = 0;”
Product: gcc
Version:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107525
Jonathan Wakely changed:
What|Removed |Added
CC||ville at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107525
Jonathan Wakely changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
This patch moves the global object for constructing the standard streams
out from and into the compiled library on targets that support
the init_priority attribute. This means that no longer
introduces a separate global constructor in each TU that includes it.
We can do this only if the
Currently __has_attribute(init_priority) always returns true, even on
targets that don't actually support init priorities, and when using
the attribute on such targets, we issue a hard error that init
priorities are unsupported. This makes it impossible to conditionally
use the attribute by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107525
--- Comment #5 from Jonathan Wakely ---
(In reply to Giuseppe D'Angelo from comment #4)
> Sorry, what I meant is, of course there is interest at keeping this code to
> compile in pre-C++20 mode, and possibly have the same semantics no matter
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107500
--- Comment #23 from R. Diez ---
Many thanks for the fix.
If you backport it to GCC 12.x, I won't be able to complain so much. ;-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107525
--- Comment #4 from Giuseppe D'Angelo ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to Giuseppe D'Angelo from comment #0)
> > So. ideally, the conversion operators should be using C++20 constraints, but
> > of course that's not
Add fcopysign.{s,d} with the names copysign{sf,df}3 so GCC will expand
__builtin_copysign{f,} to a single instruction.
Link: https://sourceware.org/pipermail/libc-alpha/2022-November/143177.html
gcc/ChangeLog:
* config/loongarch/loongarch.md (UNSPEC_FCOPYSIGN): New unspec.
On 11/3/22 19:06, David Malcolm wrote:
On Thu, 2022-11-03 at 15:59 -0400, Jason Merrill via Gcc-patches wrote:
Tested x86_64-pc-linux-gnu, OK for trunk?
-- >8 --
The c++-contracts branch uses this to retrieve the source form of the
contract predicate, to be returned by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107525
--- Comment #3 from Jonathan Wakely ---
And the spec seems wrong as well. The const overload should be constrained for
const T being convertible to const element_type*.
This should probably not compile:
#include
struct X
{
int&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107342
Aldy Hernandez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
We're missing a lot of TLC in keeping track of nonzero bits across
range-ops. It isn't an oversight, but just limited amount of hours to
implement stuff.
This patch keeps better track of the nonzero mask (really
maybe_nonzero bits as discussed) across multiplication and division
when the RHS is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107342
--- Comment #4 from CVS Commits ---
The master branch has been updated by Aldy Hernandez :
https://gcc.gnu.org/g:679be32e66428f0ba81d1c1b55f7bd47f01cb295
commit r13-3688-g679be32e66428f0ba81d1c1b55f7bd47f01cb295
Author: Aldy Hernandez
Date:
On 03/11/2022 16:19, Michael Matz via Gcc wrote:
Hello,
On Thu, 3 Nov 2022, Florian Weimer via Gcc wrote:
will not have propagated widely once GCC 13 releases, so rejecting
implicit ints in GCC 13 might be too early. GCC 14 might want to switch
to C23/C24 mode by default, activating auto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107500
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |12.3
--- Comment #22 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107525
--- Comment #2 from Jonathan Wakely ---
Also, the constraint is wrong for the non-const conversion. It checks for
convertibility to const element_type* but should be element_type*.
Tested powerpc64le-linux. Pushed to trunk.
-- >8 --
Since this is a trivial type, we probably don't need to do anything to
ensure it's still accessible after other static dtors.
libstdc++-v3/ChangeLog:
PR libstdc++/107500
* libsupc++/eh_globals.cc (eh_globals): Remove
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107511
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
Tested powerpc64le-linux. Pushed to trunk.
-- >8 --
As in r12-6867-ge20486d508afdf we need to define _GNU_SOURCE explicitly
for Cygwin, because configure finds it in libc but it isn't declared
unless we request it.
libstdc++-v3/ChangeLog:
PR libstdc++/107511
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107500
--- Comment #21 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:418999fe382c608facf57f96b53a9cb12d2fdd20
commit r13-3685-g418999fe382c608facf57f96b53a9cb12d2fdd20
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107511
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:f505f37a8e5a7646af4038b5c46f72d8a05dc7f0
commit r13-3684-gf505f37a8e5a7646af4038b5c46f72d8a05dc7f0
Author: Jonathan Wakely
From: Piotr Trojanek
Further cleanups related to warnings about unreferenced objects.
gcc/ada/
* sem_warn.adb (Check_References): Remove useless query for "spec"
of a variable; refactor nested if-statements into a single
condition.
Tested on x86_64-pc-linux-gnu,
From: Justin Squirek
Attribute Overlaps_Storage, which can appear implicitly in expansion of
aliasing checks, is now excluded from operand validity checks. Likewise
for attribute Has_Same_Storage.
gcc/ada/
* exp_attr.adb (Expand_N_Attribute_Reference): Skip operand
validity
From: Piotr Trojanek
Cleanup related to new checks for unset references.
gcc/ada/
* sem_util.adb
(In_Pragma_Expression): Add standard guard against searching too
far.
(In_Quantified_Expression): Likewise.
* sem_warn.adb
From: Eric Botcazou
The first one is that Remove_Warning_Messages reinstates the Original_Node
of an N_Raise_Constraint_Error node in the tree for no clear reasons, and
the Original_Node may contain constructs whose expansion has been stopped
when the Constraint_Error was asserted, eventually
From: Piotr Trojanek
Fix uncontroversial typos.
gcc/ada/
* doc/gnat_ugn/building_executable_programs_with_gnat.rst: Fix
typos.
* doc/gnat_ugn/elaboration_order_handling_in_gnat.rst: Fix typos
and refill as necessary; remove trailing whitespace.
*
1 - 100 of 215 matches
Mail list logo
