From: "H.J. Lu" <hjl.tools@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: libc-alpha@sourceware.org, fweimer@redhat.com, skpgkp2@gmail.com,
goldstein.w.n@gmail.com
Subject: Re: [PATCH v6] x86-64: Allocate state buffer space for RDI, RSI and RBX
Date: Tue, 19 Mar 2024 05:07:57 -0700 [thread overview]
Message-ID: <CAMe9rOq=JE5rpZ54LYhBPoG27y9vAJcBQ4t9+hQHrQVTKM5XVw@mail.gmail.com> (raw)
In-Reply-To: <mvmcyrqig52.fsf@suse.de>
On Tue, Mar 19, 2024 at 5:03 AM Andreas Schwab <schwab@suse.de> wrote:
>
> On Mär 19 2024, H.J. Lu wrote:
>
> > On Tue, Mar 19, 2024 at 4:46 AM Andreas Schwab <schwab@suse.de> wrote:
> >>
> >> On Mär 19 2024, H.J. Lu wrote:
> >>
> >> > tst-gnu2-tls2mod1.S uses RXX_LP, cfi_xxx and L from
> >> > sysdep.h. Do they depend on config.h?
> >>
> >> No, but other parts may depend on it that can cause compilation errors.
> >>
> >
> > Which configure options will cause compilation errors?
>
> It's not upstream, you can see it here:
>
> https://build.opensuse.org/package/live_build_log/home:Andreas_Schwab:glibc/glibc:testsuite/f/x86_64
>
Please open a glibc bug report with steps to reproduce the issue.
--
H.J.
next prev parent reply other threads:[~2024-03-19 12:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 13:40 [PATCH v6] x86-64: Allocate state buffer space for RDI, RSI and RBX H.J. Lu
2024-03-18 23:20 ` Sunil Pandey
2024-03-19 8:31 ` Andreas Schwab
2024-03-19 11:12 ` H.J. Lu
2024-03-19 11:21 ` Andreas Schwab
2024-03-19 11:35 ` H.J. Lu
2024-03-19 11:46 ` Andreas Schwab
2024-03-19 11:50 ` H.J. Lu
2024-03-19 12:02 ` Andreas Schwab
2024-03-19 12:07 ` H.J. Lu [this message]
2024-03-19 12:16 ` Florian Weimer
2024-03-19 12:26 ` H.J. Lu
2024-03-19 12:35 ` Andreas Schwab
2024-03-19 12:51 ` Andreas Schwab
2024-03-19 12:53 ` H.J. Lu
2024-03-19 12:55 ` H.J. Lu
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMe9rOq=JE5rpZ54LYhBPoG27y9vAJcBQ4t9+hQHrQVTKM5XVw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=fweimer@redhat.com \
--cc=goldstein.w.n@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
--cc=skpgkp2@gmail.com \
/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).