public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/111643] __attribute__((flatten)) with -O1 runs out of memory (killed cc1)
Date: Thu, 05 Oct 2023 08:26:18 +0000 [thread overview]
Message-ID: <bug-111643-4-D8mdb8VJQb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111643-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111643
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:ffbd7c3d0fd1b9b10ef5a0f2b2e64bd234620167
commit r14-4404-gffbd7c3d0fd1b9b10ef5a0f2b2e64bd234620167
Author: Richard Biener <rguenther@suse.de>
Date: Wed Oct 4 11:19:10 2023 +0200
ipa/111643 - clarify flatten attribute documentation
The following clarifies the flatten attribute documentation to mention
the inlining applies also to calls formed as part of inlining earlier
calls but not calls to the function itself.
PR ipa/111643
* doc/extend.texi (attribute flatten): Clarify.
next prev parent reply other threads:[~2023-10-05 8:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 19:49 [Bug c/111643] New: " lukas.graetz@tu-darmstadt.de
2023-09-29 19:52 ` [Bug ipa/111643] " pinskia at gcc dot gnu.org
2023-09-29 20:39 ` glisse at gcc dot gnu.org
2023-09-30 6:19 ` lukas.graetz@tu-darmstadt.de
2023-10-01 0:53 ` lukas.graetz@tu-darmstadt.de
2023-10-01 1:13 ` pinskia at gcc dot gnu.org
2023-10-04 9:21 ` rguenth at gcc dot gnu.org
2023-10-05 8:26 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-05 9:02 ` rguenth at gcc dot gnu.org
2023-10-06 16:34 ` lukas.graetz@tu-darmstadt.de
2023-10-06 16:45 ` amonakov at gcc dot gnu.org
2023-10-06 21:31 ` lukas.graetz@tu-darmstadt.de
2023-10-06 21:37 ` pinskia at gcc dot gnu.org
2023-10-06 21:40 ` pinskia at gcc dot gnu.org
2023-10-06 22:03 ` lukas.graetz@tu-darmstadt.de
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-111643-4-D8mdb8VJQb@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).