public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102472] Infinite loop on m68k
Date: Thu, 23 Sep 2021 19:25:05 +0000 [thread overview]
Message-ID: <bug-102472-4-nhgtLOlkJF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102472-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102472
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-09-23
Component|c |target
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
Keywords| |compile-time-hog
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>In this case that we have an infinite loop, I don't know how provide .i and .s files. Can you please point me some instruction for this case?
https://gcc.gnu.org/bugs/ has instructions on how to get the .i file.
Basically add -save-temps to gcc command line (add -v too)
next prev parent reply other threads:[~2021-09-23 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 16:26 [Bug c/102472] New: " giulio.benetti at benettiengineering dot com
2021-09-23 19:25 ` pinskia at gcc dot gnu.org [this message]
2021-09-23 20:01 ` [Bug target/102472] " giulio.benetti at benettiengineering dot com
2021-09-23 20:03 ` giulio.benetti at benettiengineering dot com
2021-09-23 20:03 ` giulio.benetti at benettiengineering dot com
2021-09-23 23:51 ` pinskia at gcc dot gnu.org
2021-09-24 7:04 ` rguenth at gcc dot gnu.org
2021-09-24 21:20 ` giulio.benetti at benettiengineering dot com
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-102472-4-nhgtLOlkJF@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).