From: Xi Ruoyao <xry111@xry111.site>
To: enric - serverand <enric@serverand.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: error -mno-unaligned-access unrecognized command-line option
Date: Thu, 07 Jul 2022 23:54:55 +0800 [thread overview]
Message-ID: <1fe2482f75c17d8107542eee68e579de3837d537.camel@xry111.site> (raw)
In-Reply-To: <2b7c5840-788a-eaf9-2155-64afded020c5@serverand.com>
On Thu, 2022-07-07 at 17:46 +0200, enric - serverand wrote:
>
> El 7/7/22 a les 16:31, Xi Ruoyao ha escrit:
> > On Thu, 2022-07-07 at 16:23 +0200, enric - serverand wrote:
> > > El 7/7/22 a les 3:59, Xi Ruoyao ha escrit:
> > > > On Wed, 2022-07-06 at 22:55 +0200, enric - serverand wrote:
> > > > > Hello!
> > > > >
> > > > > unrecognized command-line option -mno-unaligned-access
> > > > It's a target specific option and not available for all targets.
> > > Thank you very much for responding.
> > > I try to compile with GCC on Debian Bullseye (11). Can I try an
> > > equivalent option, thank you.
> > What CPU does GCC target to?
> an X86_64 (linux).
It's not possible then.
AGAIN:
Please keep gcc-help as recipient or CC. You can't assume I (or anyone)
can answer all the following questions personally just because I've
answered one.
If you keep ignoring my words I'll not reply anymore.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2022-07-07 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 20:55 enric - serverand
2022-07-07 1:59 ` Xi Ruoyao
[not found] ` <11e63da3-8371-f0ed-8107-9c5d6ccf8fbb@serverand.com>
2022-07-07 14:31 ` Xi Ruoyao
[not found] ` <2b7c5840-788a-eaf9-2155-64afded020c5@serverand.com>
2022-07-07 15:54 ` Xi Ruoyao [this message]
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=1fe2482f75c17d8107542eee68e579de3837d537.camel@xry111.site \
--to=xry111@xry111.site \
--cc=enric@serverand.com \
--cc=gcc-help@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).