public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107874] merge not using all its arguments
Date: Thu, 01 Dec 2022 23:54:01 +0000 [thread overview]
Message-ID: <bug-107874-4-1hut6LhpjW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107874-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107874
--- Comment #13 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
A debug session gives:
(gdb) c
Continuing.
^C
Program received signal SIGINT, Interrupt.
futex_wait (private=0, expected=2, futex_word=0x405950) at
../sysdeps/nptl/futex-internal.h:146
146 int err = lll_futex_timed_wait (futex_word, expected, NULL, private);
(gdb) bt
#0 futex_wait (private=0, expected=2, futex_word=0x405950)
at ../sysdeps/nptl/futex-internal.h:146
#1 __GI___lll_lock_wait (futex=futex@entry=0x405950, private=0)
at lowlevellock.c:49
#2 0x00007ffff79d1432 in lll_mutex_lock_optimized (mutex=0x405950)
at pthread_mutex_lock.c:48
#3 ___pthread_mutex_lock (mutex=0x405950) at pthread_mutex_lock.c:93
#4 0x00007ffff7e73503 in __gthread_mutex_lock (__mutex=0x405950)
at ../libgcc/gthr-default.h:749
#5 get_gfc_unit (n=6, do_create=1) at ../../../trunk/libgfortran/io/unit.c:395
#6 0x00007ffff7e71b85 in data_transfer_init (dtp=0x7fffffffd9d0, read_flag=0)
at ../../../trunk/libgfortran/io/transfer.c:3007
#7 0x00000000004017dd in testmerge9::tstuff () at merge_1.f90:39
#8 0x000000000040128c in testmerge9 () at merge_1.f90:14
#9 0x000000000040184f in main (argc=1, argv=0x7fffffffe2c4) at merge_1.f90:36
#10 0x00007ffff796a510 in __libc_start_call_main (
main=main@entry=0x40181b <main>, argc=argc@entry=1,
argv=argv@entry=0x7fffffffdfa8)
at ../sysdeps/nptl/libc_start_call_main.h:58
#11 0x00007ffff796a5c9 in __libc_start_main_impl (main=0x40181b <main>,
argc=1, argv=0x7fffffffdfa8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffffffdf98)
at ../csu/libc-start.c:381
I would speculate we are trashing some memory since there is no reason to hang
in there.
next prev parent reply other threads:[~2022-12-01 23:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 4:57 [Bug fortran/107874] New: " john.harper at vuw dot ac.nz
2022-11-26 20:30 ` [Bug fortran/107874] " anlauf at gcc dot gnu.org
2022-11-27 1:03 ` kargl at gcc dot gnu.org
2022-11-27 20:00 ` anlauf at gcc dot gnu.org
2022-11-27 21:07 ` anlauf at gcc dot gnu.org
2022-11-27 21:24 ` sgk at troutmask dot apl.washington.edu
2022-11-28 20:07 ` anlauf at gcc dot gnu.org
2022-11-29 18:19 ` cvs-commit at gcc dot gnu.org
2022-12-01 20:28 ` anlauf at gcc dot gnu.org
2022-12-01 21:36 ` jvdelisle2 at gmail dot com
2022-12-01 21:55 ` anlauf at gcc dot gnu.org
2022-12-01 22:17 ` anlauf at gcc dot gnu.org
2022-12-01 23:46 ` jvdelisle at gcc dot gnu.org
2022-12-01 23:54 ` jvdelisle at gcc dot gnu.org [this message]
2022-12-02 0:34 ` jvdelisle at gcc dot gnu.org
2022-12-02 17:48 ` anlauf at gcc dot gnu.org
2022-12-02 19:44 ` jvdelisle at gcc dot gnu.org
2022-12-02 20:22 ` anlauf at gcc dot gnu.org
2022-12-02 20:50 ` john.harper at vuw dot ac.nz
2022-12-02 21:05 ` anlauf at gcc dot gnu.org
2022-12-02 21:26 ` anlauf at gcc dot gnu.org
2022-12-02 21:27 ` john.harper at vuw dot ac.nz
2022-12-02 21:35 ` cvs-commit at gcc dot gnu.org
2022-12-02 21:42 ` jvdelisle at gcc dot gnu.org
2022-12-07 21:22 ` anlauf 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-107874-4-1hut6LhpjW@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).