public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/115528] [15 regression] segmentation fault in legacy F77 code Date: Tue, 18 Jun 2024 21:54:05 +0000 [thread overview] Message-ID: <bug-115528-4-4uf0ta3BAF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115528-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528 --- Comment #7 from Jürgen Reuter <juergen.reuter at desy dot de> --- First data point: after the commit from Uros, https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=8bb6b2f4ae19c3aab7d7a5e5c8f5965f89d90e01 at Sun, 9 Jun 2024 10:09:13 all was still fine.
next prev parent reply other threads:[~2024-06-18 21:54 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-17 20:56 [Bug fortran/115528] New: " juergen.reuter at desy dot de 2024-06-17 21:01 ` [Bug fortran/115528] " pinskia at gcc dot gnu.org 2024-06-17 21:18 ` juergen.reuter at desy dot de 2024-06-18 6:31 ` [Bug middle-end/115528] " rguenth at gcc dot gnu.org 2024-06-18 10:47 ` juergen.reuter at desy dot de 2024-06-18 17:50 ` kargls at comcast dot net 2024-06-18 21:52 ` juergen.reuter at desy dot de 2024-06-18 21:54 ` juergen.reuter at desy dot de [this message] 2024-06-19 6:11 ` juergen.reuter at desy dot de 2024-06-19 9:30 ` juergen.reuter at desy dot de 2024-06-19 11:53 ` juergen.reuter at desy dot de 2024-06-19 13:49 ` juergen.reuter at desy dot de 2024-06-19 13:53 ` sjames at gcc dot gnu.org 2024-06-20 5:45 ` juergen.reuter at desy dot de 2024-06-20 7:15 ` juergen.reuter at desy dot de 2024-06-20 7:36 ` juergen.reuter at desy dot de 2024-06-20 9:17 ` [Bug middle-end/115528] [15 regression] segmentation fault in legacy F77 code since r15-1238-g1fe55a1794863b rguenth at gcc dot gnu.org 2024-06-20 10:08 ` juergen.reuter at desy dot de 2024-06-20 11:20 ` rguenth at gcc dot gnu.org 2024-06-20 22:55 ` juergen.reuter at desy dot de 2024-06-21 5:26 ` kargls at comcast dot net 2024-06-21 10:30 ` rguenth at gcc dot gnu.org 2024-06-21 11:19 ` rguenth at gcc dot gnu.org 2024-06-22 13:23 ` juergen.reuter at desy dot de 2024-06-22 13:27 ` rguenth at gcc dot gnu.org 2024-06-22 13:29 ` juergen.reuter at desy dot de 2024-06-22 13:33 ` juergen.reuter at desy dot de 2024-06-22 13:34 ` juergen.reuter at desy dot de 2024-06-24 6:54 ` juergen.reuter at desy dot de 2024-06-24 7:25 ` rguenth at gcc dot gnu.org 2024-06-24 11:28 ` cvs-commit at gcc dot gnu.org 2024-06-24 11:29 ` rguenth 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-115528-4-4uf0ta3BAF@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: linkBe 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).