From: Neil Carlson <neil.n.carlson@gmail.com>
To: fortran@gcc.gnu.org
Subject: Recommended developer options when building GCC from source
Date: Sat, 6 Apr 2024 17:54:43 -0600 [thread overview]
Message-ID: <CABkMBNKmDFGziGNu-HC+JW1DBwA6kCGYYNc7YbfJ7iqH4kT+rA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
What are the recommended options to use (e.g., --enable-libsanitize) when
building GCC from source for the purpose of locating gfortran bugs? I'm
trying to pin down a runtime memory corruption error, and I recall seeing
at various times in the past recommendations for creating a suitable
gfortran build and the associated gfortran command line options for dumping
internal info, but I can't seem to find that info now.
Thanks!
next reply other threads:[~2024-04-06 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 23:54 Neil Carlson [this message]
2024-04-07 3:31 ` Jerry D
2024-04-10 18:19 ` Steve Kargl
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=CABkMBNKmDFGziGNu-HC+JW1DBwA6kCGYYNc7YbfJ7iqH4kT+rA@mail.gmail.com \
--to=neil.n.carlson@gmail.com \
--cc=fortran@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).