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 fortran/114859] Seeing new segmentation fault in same_type_as
Date: Fri, 26 Apr 2024 07:48:35 +0000 [thread overview]
Message-ID: <bug-114859-4-yl681VOuyx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114859-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114859
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> ---
The Fedora versions don't provide any information to upstream,
14.0.1-0.13.fc40 is r14-9704 and 14.0.1-0.15.fc40 is r14-9924
next prev parent reply other threads:[~2024-04-26 7:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 3:59 [Bug fortran/114859] New: " orion at nwra dot com
2024-04-26 7:48 ` jakub at gcc dot gnu.org [this message]
2024-04-26 7:55 ` [Bug fortran/114859] " jakub at gcc dot gnu.org
2024-04-26 8:03 ` jakub at gcc dot gnu.org
2024-04-26 15:48 ` jakub at gcc dot gnu.org
2024-04-26 16:50 ` [Bug fortran/114859] [14 Regression] Seeing new segmentation fault in same_type_as since r14-9752 jakub at gcc dot gnu.org
2024-04-26 16:55 ` jakub at gcc dot gnu.org
2024-04-26 16:59 ` jakub at gcc dot gnu.org
2024-04-26 17:10 ` jakub at gcc dot gnu.org
2024-04-26 18:07 ` [Bug fortran/114859] [14/15 " jakub at gcc dot gnu.org
2024-04-26 18:27 ` jakub at gcc dot gnu.org
2024-04-27 14:50 ` pault at gcc dot gnu.org
2024-04-27 18:58 ` jakub at gcc dot gnu.org
2024-04-28 5:37 ` pault at gcc dot gnu.org
2024-04-28 21:19 ` pault at gcc dot gnu.org
2024-04-29 9:11 ` jakub at gcc dot gnu.org
2024-04-29 11:06 ` pault at gcc dot gnu.org
2024-04-29 18:45 ` anlauf at gcc dot gnu.org
2024-04-30 8:21 ` jakub at gcc dot gnu.org
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-114859-4-yl681VOuyx@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).