On Thu, 18 Apr 2024 at 07:06, Thomas Koenig via Gcc wrote:
>
> Am 18.04.24 um 01:27 schrieb Mark Wielaard:
> > We also should make sure that all generated files (either in git or in
> > the release/snapshot tar balls) can be reliably and reproducibly
> > regenerated. This also helps the (pre-commi
On 4/18/24 13:41, Arnd Bergmann wrote:
On Thu, Apr 18, 2024, at 17:44, Joseph Myers wrote:
On Wed, 17 Apr 2024, Sandra Loosemore wrote:
Therefore I'd like to mark Nios II as obsolete in GCC 14 now, and remove
support from all toolchain components after the release is made. I'm not sure
the
Hi Frank,
> - just send the emails immediately, without the daemon stuff; if the
> delays are there to try to sequentialize them, consider instead
> getting the hooks to emit Message-Id:/In-Reply-To:/Date: headers to
> let MUA's sort properly at reception
We can certainly add a non-daemon m
Hi, Joel -
> [...] Thinking more long term, I think there are talks about using
> a more comprehensive system for source and contribution management,
> similar to products such as GitLab or GitHub. [...]
(Yeah, but I wouldn't count on any of that in the medium term.)
> [...] That's why I tend
Hi,
While testing with -Wformat=2, I encountered the following behaviour:
Please see the attached simple C file (tested on gcc 11.2.0/gcc
13.2.1), both give the same warning (clang (17.0.6/gives no warning,
although I am not really sure they have the same effect with the
flags).
It gives the fol
Snapshot gcc-12-20240419 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20240419/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
