public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113059] [14 regression] fftw fails tests for -O3 -m32 -march=znver2 since r14-6210-ge44ed92dbbe9d4
Date: Fri, 22 Dec 2023 18:41:31 +0000 [thread overview]
Message-ID: <bug-113059-4-ihZLcikg3P@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113059-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113059
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Florian Weimer from comment #8)
> (In reply to Jakub Jelinek from comment #3)
> > Seems the package's configure is affected by most likely the modern C
> > changes,
> > I see
> > --- config.h.good 2023-12-22 17:47:44.615207332 +0100
> > +++ config.h.bad 2023-12-22 17:46:42.304068624 +0100
> > @@ -37,7 +37,7 @@
> > /* #undef F77_FUNC_ */
> >
> > /* Define if F77_FUNC and F77_FUNC_ are equivalent. */
> > -/* #undef F77_FUNC_EQUIV */
> > +#define F77_FUNC_EQUIV 1
> >
> > /* Define if F77 and FC dummy `main' functions are identical. */
> > /* #undef FC_DUMMY_MAIN_EQ_F77 */
> > @@ -404,7 +404,7 @@
> >
> > /* Include g77-compatible wrappers in addition to any other Fortran
> > wrappers.
> > */
> > -/* #undef WITH_G77_WRAPPERS */
> > +#define WITH_G77_WRAPPERS 1
> >
> > /* Use our own aligned malloc routine; mainly helpful for Windows systems
> > lacking aligned allocation system-library routines. */
> > diff in config.h between my system gcc 12 and gcc 14 snapshot.
> > But that isn't the reason for the failure.
>
> I don't see a different to system gcc 13. It has F77_FUNC_EQUIV and
> WITH_G77_WRAPPERS set as well. Do you see this for all build variants of
> fftw?
Ah, seems I don't have system gfortran installed, which is probably the cause
of the config.h difference. Sorry for the false alarm.
next prev parent reply other threads:[~2023-12-22 18:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 9:12 [Bug target/113059] New: " sjames at gcc dot gnu.org
2023-12-18 9:30 ` [Bug target/113059] " rguenth at gcc dot gnu.org
2023-12-22 9:47 ` jakub at gcc dot gnu.org
2023-12-22 13:55 ` sjames at gcc dot gnu.org
2023-12-22 16:51 ` jakub at gcc dot gnu.org
2023-12-22 17:57 ` jakub at gcc dot gnu.org
2023-12-22 18:11 ` jakub at gcc dot gnu.org
2023-12-22 18:11 ` jakub at gcc dot gnu.org
2023-12-22 18:14 ` jakub at gcc dot gnu.org
2023-12-22 18:30 ` fw at gcc dot gnu.org
2023-12-22 18:40 ` jakub at gcc dot gnu.org
2023-12-22 18:41 ` jakub at gcc dot gnu.org [this message]
2024-01-09 16:03 ` jakub at gcc dot gnu.org
2024-01-10 9:10 ` rguenth at gcc dot gnu.org
2024-01-10 9:19 ` jakub at gcc dot gnu.org
2024-01-10 9:53 ` rguenther at suse dot de
2024-01-10 18:24 ` pinskia at gcc dot gnu.org
2024-01-30 7:59 ` sjames at gcc dot gnu.org
2024-01-30 9:23 ` jakub at gcc dot gnu.org
2024-01-30 10:25 ` rguenth at gcc dot gnu.org
2024-01-30 10:32 ` jakub at gcc dot gnu.org
2024-01-30 10:45 ` jakub at gcc dot gnu.org
2024-01-30 10:46 ` rguenther at suse dot de
2024-01-30 10:47 ` rguenth at gcc dot gnu.org
2024-01-30 11:17 ` jakub at gcc dot gnu.org
2024-01-30 11:39 ` jakub at gcc dot gnu.org
2024-02-05 8:36 ` cvs-commit at gcc dot gnu.org
2024-02-05 8:38 ` [Bug target/113059] [15 " jakub at gcc dot gnu.org
2024-02-23 15:49 ` sjames at gcc dot gnu.org
2024-02-23 15:49 ` sjames at gcc dot gnu.org
2024-03-06 16:44 ` sjames 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-113059-4-ihZLcikg3P@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).