public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/114658] branch "releases/gcc-13" builds "gcc version 14.0.1 (experimental)"
Date: Tue, 09 Apr 2024 15:22:49 +0000 [thread overview]
Message-ID: <bug-114658-4-dGHPC1tDMB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114658-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114658
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
That doesn't seem possible.
Are you sure you've correctly checked out the releases/gcc-13 branch?
That branch should contain gcc/BASE-VER with 13.2.1 in it and the resulting
compiler should report that, like in:
./xgcc -B ./ -v
Reading specs from ./specs
COLLECT_GCC=./xgcc
COLLECT_LTO_WRAPPER=./lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../configure
--enable-languages=default,ada,obj-c++,lto,go,d,m2
--enable-checking=yes,rtl,extra --enable-libstdcxx-backtrace=yes
--with-isl=/usr/src/isl-0.24/obji/
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.1 20240329 (GCC)
next prev parent reply other threads:[~2024-04-09 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 15:05 [Bug driver/114658] New: " felix-gcc at fefe dot de
2024-04-09 15:22 ` jakub at gcc dot gnu.org [this message]
2024-04-09 17:25 ` [Bug driver/114658] " felix-gcc at fefe dot de
2024-04-09 17:37 ` felix-gcc at fefe dot de
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=bug-114658-4-dGHPC1tDMB@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).