public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steinhelten at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/108249] cc1plus segmentation fault compiling Marlin on RPI3
Date: Wed, 28 Dec 2022 22:02:32 +0000 [thread overview]
Message-ID: <bug-108249-4-vAWfRFD1FW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108249-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108249
--- Comment #3 from John Lind <steinhelten at gmail dot com> ---
I'm not sure how to get that, since I am invoking it through
platformio. What I am entering is:
/home/pi/.platformio/penv/bin/platformio run --verbose
I don't know how to get platformio to show the compiler invocation,
except I THINK that the "build_flags" is most of it.
On Wed, Dec 28, 2022 at 3:53 PM pinskia at gcc dot gnu.org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108249
>
> Andrew Pinski <pinskia at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Last reconfirmed| |2022-12-28
> Ever confirmed|0 |1
> Status|UNCONFIRMED |WAITING
>
> --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> Can you provide the full command line which is failing?
>
> --
> You are receiving this mail because:
> You reported the bug.
next prev parent reply other threads:[~2022-12-28 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 21:48 [Bug middle-end/108249] New: " steinhelten at gmail dot com
2022-12-28 21:53 ` [Bug middle-end/108249] " pinskia at gcc dot gnu.org
2022-12-28 21:57 ` steinhelten at gmail dot com
2022-12-28 22:02 ` steinhelten at gmail dot com [this message]
2023-01-07 20:58 ` steinhelten at gmail dot com
2023-01-07 21:00 ` 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-108249-4-vAWfRFD1FW@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).