From: "HON LUU" <hon@dreambigsemi.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: gcc question
Date: Wed, 8 Sep 2021 16:27:54 +0000 [thread overview]
Message-ID: <VI1PR02MB3118398D238B522642F28FBBDDD49@VI1PR02MB3118.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <20210908162025.GO1583@gate.crashing.org>
I am confused. I saw the rest of your response.
Let me go through it.
Regards,
Hon
Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Segher Boessenkool <segher@kernel.crashing.org>
Sent: Wednesday, September 8, 2021 9:20:25 AM
To: HON LUU <hon@dreambigsemi.com>
Cc: gcc-help@gcc.gnu.org <gcc-help@gcc.gnu.org>
Subject: Re: gcc question
Hi!
On Wed, Sep 08, 2021 at 03:06:54PM +0000, HON LUU wrote:
> + The modified gcc command did not compile. The error message would look like this.
> In file included from ././include/linux/compiler_types.h:58,
> from <command-line>:
> ./arch/x86/include/asm/jump_label.h: In function ‘unmap_user_buf.part.3’:
> ./include/linux/compiler-gcc.h:305:38: error: asm operand 0 probably doesn’t match constraints [-Werror]
> #define asm_volatile_goto(x...) do { asm goto(x); asm (""); } while (0)
> ^~~
> ./arch/x86/include/asm/jump_label.h:38:2: note: in expansion of macro ‘asm_volatile_goto’
> asm_volatile_goto("1:"
> ^~~~~~~~~~~~~~~~~
> ./include/linux/compiler-gcc.h:305:38: error: impossible constraint in ‘asm’
> #define asm_volatile_goto(x...) do { asm goto(x); asm (""); } while (0)
> ^~~
> ./arch/x86/include/asm/jump_label.h:38:2: note: in expansion of macro ‘asm_volatile_goto’
> asm_volatile_goto("1:"
> ^~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
(Use LANG=C or LC_ALL=C to not get those weird quotes, just like you
would use this to get error messages that aren't translated, that the
compiler developers can actually read :-) )
You need to show the full code of the asm_volatile_goto, and the
declarations of everything used in its operands, for us to get a handle
on what is going on here. Bonus points if you manage to make a stand-
alone compilable testcase that shows the problem.
GL;HF,
Segher
next prev parent reply other threads:[~2021-09-08 16:27 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 [this message]
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 ` HON LUU
2021-09-13 19:42 ` Florian Weimer
2021-09-13 19:50 ` HON LUU
2021-09-13 19:51 ` Florian Weimer
2021-09-13 19:52 ` 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=VI1PR02MB3118398D238B522642F28FBBDDD49@VI1PR02MB3118.eurprd02.prod.outlook.com \
--to=hon@dreambigsemi.com \
--cc=gcc-help@gcc.gnu.org \
--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).