public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "natalie.perlin at noaa dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/115107] f951: internal compiler error: Segmentation fault 0xcf878f crash_signal toplev.cc:314
Date: Wed, 22 May 2024 07:55:47 +0000	[thread overview]
Message-ID: <bug-115107-4-WQ9JCiLroe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115107-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115107

--- Comment #10 from Natalie Perlin <natalie.perlin at noaa dot gov> ---
A workaround found for gnu/14.1.0 gcc that produces error instead of warnings
at times: 
 Using cflag="-Wno-implicit-function-declaration ..." helped to avoid errors in
the code location in my previous comment.

The following "cflags" was needed to build successfully a package of the
software stack that gave troubles compiling:

 cflags="Wno-deprecated-declarations -Wno-implicit-function-declaration
-Wno-incompatible-pointer-types -Wno-implicit-int"

  parent reply	other threads:[~2024-05-22  7:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 16:53 [Bug fortran/115107] New: " natalie.perlin at noaa dot gov
2024-05-15 16:56 ` [Bug fortran/115107] " jakub at gcc dot gnu.org
2024-05-15 17:01 ` jakub at gcc dot gnu.org
2024-05-15 17:15 ` rguenth at gcc dot gnu.org
2024-05-15 18:13 ` anlauf at gcc dot gnu.org
2024-05-16  4:29 ` natalie.perlin at noaa dot gov
2024-05-16  7:08 ` natalie.perlin at noaa dot gov
2024-05-16  7:20 ` natalie.perlin at noaa dot gov
2024-05-16 17:06 ` anlauf at gcc dot gnu.org
2024-05-16 18:26 ` natalie.perlin at noaa dot gov
2024-05-22  6:16 ` natalie.perlin at noaa dot gov
2024-05-22  7:55 ` natalie.perlin at noaa dot gov [this message]
2024-05-22  8:00 ` jakub at gcc dot gnu.org
2024-05-22 15:14 ` natalie.perlin at noaa dot gov
2024-05-22 15:23 ` jakub at gcc dot gnu.org
2024-05-22 17:11 ` anlauf at gcc dot gnu.org
2024-05-25 18:54 ` natalie.perlin at noaa dot gov
2024-05-26 18:38 ` anlauf at gcc dot gnu.org
2024-05-29 15:23 ` natalie.perlin at noaa dot gov
2024-05-29 15:30 ` jakub 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-115107-4-WQ9JCiLroe@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).