From: Michael Matz <matz@suse.de>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
Ard Biesheuvel <ardb+git@google.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Ard Biesheuvel <ardb@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Song Liu <song@kernel.org>, Ricardo Ribalda <ribalda@kernel.org>,
Fangrui Song <maskray@google.com>,
Arthur Eubanks <aeubanks@google.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] x86/purgatory: Switch to the position-independent small code model
Date: Tue, 30 Apr 2024 15:15:47 +0200 (CEST) [thread overview]
Message-ID: <5199b4f0-b4c7-5ef4-e8b7-0ade7c533edd@suse.de> (raw)
In-Reply-To: <4ce6cf96-685d-4792-b2fd-949c07eff707@kernel.org>
Hello,
On Tue, 30 Apr 2024, Jiri Slaby wrote:
> >> Interesting. I thought gcc doesn't have problems here yet and was
> >> talking to Matz on Thu about it and it seems he's forgotten about his
> >> statement too that "you should simply stop using -mcmodel=large. Noone
> >> should use it." :-)
> >
> > It may be so ingrained in my brain that I'm not _always_ saying it when
> > talking about the large code model over a beer. And indeed I know of no
> > particular problems with it vis GCC,
>
> Of course you do :).
:-P
> That bsc#1211853 I linked earlier. I.e. gcc-13 +
> -fstrict-flex-arrays=3 + -mcmodel=large + some asm() expecting __FILE__ to be
> constant (not true with the large model).
"asm() expecting $whatever" - clearly a user problem, not a GCC problem
;-)
Ciao,
Michael.
prev parent reply other threads:[~2024-04-30 13:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 20:17 [PATCH] x86/purgatory: Switch to the position-independent small code model Ard Biesheuvel
2024-04-18 20:36 ` Nick Desaulniers
2024-04-18 20:46 ` Fangrui Song
2024-04-20 15:29 ` Borislav Petkov
2024-04-20 15:51 ` Ard Biesheuvel
2024-04-18 20:37 ` Nathan Chancellor
2024-04-19 11:35 ` Jiri Slaby
2024-04-20 13:17 ` Borislav Petkov
2024-04-29 12:05 ` Michael Matz
2024-04-29 12:30 ` Borislav Petkov
2024-04-30 5:15 ` Jiri Slaby
2024-04-30 13:15 ` Michael Matz [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=5199b4f0-b4c7-5ef4-e8b7-0ade7c533edd@suse.de \
--to=matz@suse.de \
--cc=aeubanks@google.com \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=jirislaby@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maskray@google.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ribalda@kernel.org \
--cc=song@kernel.org \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.