public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/113291] New: [14 Regression] compilation never (?) finishes with recursive always_inline functions at -O and above
Date: Tue, 09 Jan 2024 14:00:51 +0000	[thread overview]
Message-ID: <bug-113291-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113291
           Summary: [14 Regression] compilation never (?) finishes with
                    recursive always_inline functions at -O and above
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu

Created attachment 57015
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57015&action=edit
reduced testcase

Compiler output:
$ time x86_64-pc-linux-gnu-gcc -O testcase.c -Wall -W
testcase.c:13:1: warning: 'always_inline' function might not be inlinable
[-Wattributes]
   13 | f1 (void)
      | ^~
testcase.c:6:1: warning: 'always_inline' function might not be inlinable
[-Wattributes]
    6 | f0 (void)
      | ^~
testcase.c: In function 'f0':
testcase.c:6:1: warning: infinite recursion detected [-Winfinite-recursion]
In function 'f1',
    inlined from 'f0' at testcase.c:8:3:
testcase.c:16:3: note: recursive call
   16 |   f0 ();
      |   ^~~~~
testcase.c: In function 'f1':
testcase.c:13:1: warning: infinite recursion detected [-Winfinite-recursion]
   13 | f1 (void)
      | ^~
testcase.c:15:3: note: recursive call
   15 |   f1 ();
      |   ^~~~~
^C

real    1m21.533s
user    0m0.002s
sys     0m0.000s


$ x86_64-pc-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r14-7023-20240109134751-gab6224dfe12-checking-yes-rtl-df-extra-nobootstrap-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--disable-bootstrap --with-cloog --with-ppl --with-isl
--build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
--target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r14-7023-20240109134751-gab6224dfe12-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20240109 (experimental) (GCC)

             reply	other threads:[~2024-01-09 14:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09 14:00 zsojka at seznam dot cz [this message]
2024-01-09 17:55 ` [Bug ipa/113291] " pinskia at gcc dot gnu.org
2024-01-09 18:38 ` pinskia at gcc dot gnu.org
2024-01-10 13:15 ` [Bug ipa/113291] [14 Regression] compilation never (?) finishes with recursive always_inline functions at -O and above since r14-2172 jakub at gcc dot gnu.org
2024-01-11 12:14 ` rguenth at gcc dot gnu.org
2024-02-14 16:07 ` hubicka at gcc dot gnu.org
2024-02-14 16:26 ` hubicka at gcc dot gnu.org
2024-02-14 17:14 ` hubicka at gcc dot gnu.org
2024-03-26 10:41 ` rguenth at gcc dot gnu.org
2024-04-09  9:50 ` hubicka at gcc dot gnu.org
2024-04-18 13:42 ` law at gcc dot gnu.org
2024-05-07  7:43 ` [Bug ipa/113291] [14/15 " rguenth at gcc dot gnu.org
2024-05-14 10:59 ` cvs-commit 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-113291-4@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).