From: Florian Weimer <fweimer@redhat.com>
To: "HON LUU" <hon@dreambigsemi.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: gcc question
Date: Mon, 13 Sep 2021 21:42:49 +0200 [thread overview]
Message-ID: <87pmtc6z46.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <VI1PR02MB31187F8FA0230724550E78F2DDD99@VI1PR02MB3118.eurprd02.prod.outlook.com> (HON LUU's message of "Mon, 13 Sep 2021 19:40:53 +0000")
* HON LUU:
> Yes, understood the point. I would have to "not using -fPIC" if I
> could not found any way out. Anyway if I willing to change the asm
> function to change the constraint to something different from "i"
> (immediate), I wonder if the question is still proper.
Are you building userspace code or kernel code? Why do you end up
compiling arch_static_branch?
Thanks,
Florian
next prev parent reply other threads:[~2021-09-13 19:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 15:06 HON LUU
2021-09-08 16:20 ` Segher Boessenkool
2021-09-08 16:26 ` HON LUU
2021-09-08 16:27 ` HON LUU
2021-09-08 17:05 ` HON LUU
2021-09-08 23:13 ` HON LUU
2021-09-10 17:58 ` HON LUU
2021-09-10 18:36 ` Segher Boessenkool
2021-09-11 21:08 ` HON LUU
2021-09-13 19:10 ` HON LUU
2021-09-13 19:22 ` Florian Weimer
2021-09-13 19:40 ` HON LUU
2021-09-13 19:42 ` Florian Weimer [this message]
2021-09-13 19:50 ` HON LUU
2021-09-13 19:51 ` Florian Weimer
2021-09-13 19:52 ` HON LUU
2021-09-13 19:42 ` HON LUU
-- strict thread matches above, loose matches on Subject: below --
2006-02-26 22:53 Brendan Darrer
2006-02-26 23:52 ` Ernest L. Williams Jr.
2006-02-27 15:29 ` Brian Budge
2002-06-12 9:29 j y
2002-06-12 11:16 ` Shawn Starr
2001-07-20 4:35 Steve Kieu
2000-08-13 19:34 tao tong
2000-04-10 7:46 GCC question Gibson, Terry
2000-04-10 8:12 ` Alexandre Oliva
2000-01-06 15:46 Black, Christopher T
2000-04-01 0:00 ` Black, Christopher T
[not found] <947048956.20674.ezmlm@gcc.gnu.org>
2000-01-04 21:22 ` John Ratcliff
2000-04-01 0:00 ` John Ratcliff
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=87pmtc6z46.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=hon@dreambigsemi.com \
--cc=segher@kernel.crashing.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).