From: Xi Ruoyao <xry111@xry111.site>
To: Lulu Cheng <chenglulu@loongson.cn>
Cc: gcc-patches@gcc.gnu.org, WANG Xuerui <i@xen0n.name>,
Chenghua Xu <xuchenghua@loongson.cn>,
Yujie Yang <yangyujie@loongson.cn>,
Mike Stump <mikestump@comcast.net>
Subject: Re: [PATCH 0/2] LoongArch: testsuite: Fix tests related to stack
Date: Mon, 06 Mar 2023 11:16:33 +0800 [thread overview]
Message-ID: <f98e9d550f35c8bf41b71cb376e49056b581d553.camel@xry111.site> (raw)
In-Reply-To: <87e2942cfc448710c4759aedbbe0f34f05a76aeb.camel@xry111.site>
On Mon, 2023-03-06 at 10:48 +0800, Xi Ruoyao wrote:
> On Mon, 2023-03-06 at 09:15 +0800, Lulu Cheng wrote:
> >
> > 在 2023/3/6 上午12:21, Xi Ruoyao 写道:
> > > On Fri, 2023-03-03 at 08:21 -0800, Mike Stump wrote:
> > > > On Mar 3, 2023, at 12:40 AM, Xi Ruoyao via Gcc-patches
> > > > <gcc-patches@gcc.gnu.org> wrote:
> > > > > Some trivial test case fixes. Ok for trunk?
> > > > Ok.
> > > Lulu: if you don't object I'll push these two in this week.
> > >
> > > I tried to bisect for the exact point where the test cases are broken,
> > > but it turns out they are broken the first day committed (r13-4401). As
> > > the draft of r13-4401 was sent in Sept 2022 but it's committed in Nov
> > > 2022, I can only guess something had changed in the two months and broke
> > > the tests...
> >
> > Sorry for the late reply, the first patch I think is fine. But I haven't
> > reproduced the problem of the second mail.
> >
> > Is there any special option in the configuration?
>
> Oh some strange thing might be happening... I'll try to figure out what
> has caused the behavior difference.
Oh no, the difference is caused by --enable-default-pie.
Maybe I should just add -fno-PIE for the dg-options. But now I'm still
puzzled: why would -fPIE affect code generation on LoongArch? AFAIK all
the code we are generating is position independent (at least for now).
>
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-03-06 3:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 8:40 Xi Ruoyao
2023-03-03 8:40 ` [PATCH 1/2] LoongArch: testsuite: Disable stack protector for some tests Xi Ruoyao
2023-03-03 8:40 ` [PATCH 2/2] LoongArch: testsuite: Adjust stack offsets in stack-check-cfa tests Xi Ruoyao
2023-03-03 16:21 ` [PATCH 0/2] LoongArch: testsuite: Fix tests related to stack Mike Stump
2023-03-05 16:21 ` Xi Ruoyao
2023-03-06 1:15 ` Lulu Cheng
2023-03-06 2:48 ` Xi Ruoyao
2023-03-06 3:16 ` Xi Ruoyao [this message]
2023-03-06 5:59 ` Xi Ruoyao
2023-03-06 8:02 ` Xi Ruoyao
2023-03-06 8:12 ` Lulu Cheng
2023-03-06 8:18 ` Xi Ruoyao
2023-03-06 8:22 ` Lulu Cheng
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=f98e9d550f35c8bf41b71cb376e49056b581d553.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=mikestump@comcast.net \
--cc=xuchenghua@loongson.cn \
--cc=yangyujie@loongson.cn \
/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).