From: Richard Biener <richard.guenther@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH] Reset proper type on vector types (PR middle-end/88587).
Date: Wed, 16 Jan 2019 11:50:00 -0000 [thread overview]
Message-ID: <CAFiYyc0u-NQ2WGGukzxiVizwL7YtrT_+5Y_J80CrfWZUZ5On6w@mail.gmail.com> (raw)
In-Reply-To: <65b91fc9-fcf5-8b73-94dc-2a16317fc59c@suse.cz>
On Wed, Jan 16, 2019 at 10:26 AM Martin Liška <mliska@suse.cz> wrote:
>
> And there's patch with Richi's validation check that he provided.
> It fails on following 2 tests in test-suite:
>
> $ ./xgcc -B. /home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr68674.c
> DECL_MODE BLK vs TYPE_MODE V8SI [V8SI]: a
> ...
>
> $ ./xgcc -B. /home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr80583.c -c
> DECL_MODE BLK vs TYPE_MODE V8SI [V8SI]: a
> ...
>
> In both cases we access a global variable from a function with a different target
> attributes. I guess Honza has seen that in inliner.
>
> What to do with these, can it be potentially dangerous?
I guess so. There's not much we can do about this other than making
DECL_MODE dynamic the same way as TYPE_MODE. I still believe
this is the wrong direction and instead RTL expansion should properly
adjust DECL_RTL and generally on GIMPLE we shouldn't need to
commit to modes early at all...
[but then we eventually want to expose more ABI details to GIMPLE]
Richard.
>
> Thanks,
> Martin
>
next prev parent reply other threads:[~2019-01-16 11:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 9:20 Martin Liška
2019-01-16 9:26 ` Martin Liška
2019-01-16 11:50 ` Richard Biener [this message]
2019-01-16 11:59 ` Jakub Jelinek
2019-01-16 12:01 ` Richard Biener
2019-01-16 12:06 ` Richard Biener
2019-01-17 11:21 ` Martin Liška
2019-01-17 12:51 ` Richard Biener
2019-01-18 14:25 ` H.J. Lu
2019-01-18 14:30 ` H.J. Lu
2019-04-15 6:50 ` Martin Liška
2019-04-15 7:50 ` Richard Biener
2019-04-15 8:11 ` Martin Liška
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=CAFiYyc0u-NQ2WGGukzxiVizwL7YtrT_+5Y_J80CrfWZUZ5On6w@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=mliska@suse.cz \
/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).