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 fortran/115528] New: [15 regression] segmentation fault in legacy F77 code
Date: Mon, 17 Jun 2024 20:56:14 +0000 [thread overview]
Message-ID: <bug-115528-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
Bug ID: 115528
Summary: [15 regression] segmentation fault in legacy F77 code
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: juergen.reuter at desy dot de
Target Milestone: ---
Some changes in gcc/gfortran between ca. June 10 and June 17, 2024 now leeds to
segmenation faults in our application (Whizard v3.1.4, c.f.
http://whizard.hepforge.org/whizard-3.1.4.tar.gz). Note that this appears in
our functional testsuite which necessitates the OCaml compiler. The
segmentation fault appears e.g. as
#0 0x7f827594f51f in ???
at ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
#1 0x7f827a3cfd0a in curr_
at ../../../contrib/tauola/formf.f:599
#2 0x7f827a3e0e16 in dam4pi_
at ../../../contrib/tauola/tauola.f:4106
#3 0x7f827a3e1fb6 in dph4pi_
at ../../../contrib/tauola/tauola.f:4067
#4 0x7f827a3e6510 in dadnew_
at ../../../contrib/tauola/tauola.f:3667
#5 0x7f827a3e685c in dexnew_
at ../../../contrib/tauola/tauola.f:3592
#6 0x7f827a3ecc2d in dexay_
at ../../../contrib/tauola/tauola.f:525
#7 0x7f827a3eeffa in initdk_
at ../../../contrib/tauola/tauola_photos_ini.f:452
I need to come up with a workable reproducer, but that's not easy, and my time
nowadays is awfully limited. :(
next reply other threads:[~2024-06-17 20:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 20:56 juergen.reuter at desy dot de [this message]
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
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@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).