public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matthew.thompson at nasa dot gov" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/98426] find_symbol in module.c traverses O(N) part of a search tree Date: Fri, 26 Apr 2024 12:43:14 +0000 [thread overview] Message-ID: <bug-98426-4-yt84CI3nt7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98426-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98426 --- Comment #12 from Matt Thompson <matthew.thompson at nasa dot gov> --- Jerry, Actually, I took a look at my reproducer and it's not quite what I was wanting (I made a mistake in the Jinja templates). I'm going to work on it now to fix this up. And I'll look at adding the random name option as well. Back soon...
next prev parent reply other threads:[~2024-04-26 12:43 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-23 10:42 [Bug fortran/98426] New: " mscfd at gmx dot net 2020-12-28 10:29 ` [Bug fortran/98426] " mscfd at gmx dot net 2020-12-28 10:36 ` mscfd at gmx dot net 2020-12-29 11:15 ` mscfd at gmx dot net 2021-10-29 18:36 ` aldot at gcc dot gnu.org 2024-04-23 20:40 ` matthew.thompson at nasa dot gov 2024-04-23 23:26 ` jvdelisle at gcc dot gnu.org 2024-04-24 2:59 ` jvdelisle at gcc dot gnu.org 2024-04-24 3:05 ` jvdelisle at gcc dot gnu.org 2024-04-25 11:20 ` matthew.thompson at nasa dot gov 2024-04-25 16:38 ` jvdelisle at gcc dot gnu.org 2024-04-26 3:12 ` jvdelisle at gcc dot gnu.org 2024-04-26 12:43 ` matthew.thompson at nasa dot gov [this message] 2024-04-26 15:53 ` matthew.thompson at nasa dot gov 2024-04-26 15:54 ` matthew.thompson at nasa dot gov 2024-04-27 2:34 ` jvdelisle 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-98426-4-yt84CI3nt7@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).