public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "d.g.gorbachev at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/59332] Segmentation fault in inline_summary with LTO + attribute optimize Date: Fri, 29 Nov 2013 13:17:00 -0000 [thread overview] Message-ID: <bug-59332-4-662OLN1ku9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59332-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59332 --- Comment #4 from Dmitry Gorbachev <d.g.gorbachev at gmail dot com> --- > Can you expand on those shortcomings/bugs? There are LTO-related issues in GCC and LD, such as PR43038, PR56536 and others. Not all problems will be fixed soon, and more bugs will be discovered in the future. As a workaround, an attribute (a pragma) to disable LTO would come in handy. > I don't think that will ever work ;) __attribute__((optimize("lto"))) works, surprisingly!
next prev parent reply other threads:[~2013-11-29 13:17 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-28 16:43 [Bug lto/59332] New: " d.g.gorbachev at gmail dot com 2013-11-29 4:39 ` [Bug lto/59332] " d.g.gorbachev at gmail dot com 2013-11-29 6:07 ` pinskia at gcc dot gnu.org 2013-11-29 10:01 ` [Bug c/59332] " rguenth at gcc dot gnu.org 2013-11-29 13:17 ` d.g.gorbachev at gmail dot com [this message] 2013-11-29 13:22 ` mpolacek at gcc dot gnu.org 2013-11-29 14:09 ` d.g.gorbachev at gmail dot com 2021-08-08 6:32 ` [Bug lto/59332] " pinskia 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-59332-4-662OLN1ku9@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: linkBe 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).