public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/sphinx] (34 commits) Merge branch 'master' into devel/sphinx
Date: Mon, 7 Nov 2022 08:55:39 +0000 (GMT) [thread overview]
Message-ID: <20221107085539.DE504385735F@sourceware.org> (raw)
The branch 'devel/sphinx' was updated to point to:
33f5dde0cd1... Merge branch 'master' into devel/sphinx
It previously pointed to:
1b09b78ee61... Merge branch 'master' into devel/sphinx
Diff:
Summary of changes (added commits):
-----------------------------------
33f5dde... Merge branch 'master' into devel/sphinx
a8fb90e... docs: update: document sanitizers can trigger warnings (*)
33dc1ba... Mitigate clang warnings: (*)
96c0533... ada: Document that gprof won't work on windows with PIE. (*)
bcb3f09... ada: Tune hash function for cross-reference entries (*)
dc3208e... ada: Fix performance regression related to references in Re (*)
d24f279... ada: Use named notation in calls to Expand_Composite_Equali (*)
2702882... ada: New warning about noncomposing user-defined "=" (*)
9b07c17... ada: Inline composite node kind AST queries (*)
2734555... ada: Fix inherited postconditions in inlined subprograms (*)
b86ff06... ada: Fixed elaboration of CUDA programs. (*)
aa0e7d3... ada: Rework CUDA host-side invocation of device-side elabor (*)
7dee088... ada: Fix detection of external calls to protected objects i (*)
90908af... ada: Clean up unnecessary nesting in code for DLL libraries (*)
981848b... ada: Suppress warnings on derived True/False (*)
214b1cb... ada: Deconstruct Safe_To_Capture_In_Parameter_Value (*)
bb513a0... ada: Flip warning suppression routine to positive meaning (*)
72ae51d... ada: Cleanup detection of code within generic instances (*)
dcc02d3... ada: Remove redundant suppression for non-modified IN OUT p (*)
2caaa4b... ada: Reject boxes in delta array aggregates (*)
8f077c4... ada: Allow reuse of Enclosing_Declaration_Or_Statement by G (*)
f073f33... ada: Clean up unnecesary call in resolution of overloaded e (*)
4e92ad4... ada: Clean up code for visibility of generic actuals (*)
76b35e7... ada: Cleanup comment about mapping parameters when inlining (*)
748976c... ada: Put_Image aspect spec incorrectly not inherited (*)
ae39527... ada: Tune layout after switching to Ada 2022 aggregate synt (*)
f8b69d4... ada: Cleanup WITH clauses after switching from obsolescent (*)
c7e9b5e... ada: Create operator nodes in functional style (*)
03b4e4a... ada: Don't reuse operator nodes in expansion (*)
ffe889d... ada: Simplify detection of pragmas in the context items (*)
74056e9... ada: Reject misplaced pragma Obsolescent (*)
c7dc111... ada: Fix missing tag for with of an obsolescent function (*)
f74a049... ada: Remove useless validity suppression for attribute Inpu (*)
8408120... vect: Fold LEN_{LOAD,STORE} if it's for the whole vector [P (*)
(*) This commit already exists in another branch.
Because the reference `refs/heads/devel/sphinx' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
next reply other threads:[~2022-11-07 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 8:55 Martin Liska [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-28 8:02 Martin Liska
2021-06-28 11:11 Martin Liska
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221107085539.DE504385735F@sourceware.org \
--to=marxin@gcc.gnu.org \
--cc=gcc-cvs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).