From: Palmer Dabbelt <palmer@dabbelt.com>
To: jiawei@iscas.ac.cn
Cc: gcc-patches@gcc.gnu.org, kito.cheng@sifive.com, wuwei2016@iscas.ac.cn
Subject: Re: [PATCH] testsuite: Update Wconversion testcase check type.
Date: Wed, 11 May 2022 21:31:38 -0700 (PDT) [thread overview]
Message-ID: <mhng-29692201-be36-483a-800f-1f08c1243d72@palmer-mbp2014> (raw)
In-Reply-To: <k49kbomqqftfj10bjs7e8o7p.1652323041358@email.android.com>
On Wed, 11 May 2022 19:37:21 PDT (-0700), jiawei@iscas.ac.cn wrote:
> Thank you, it hasn't commited into the trunk yet.
Should be now.
>
> ISCAS
>
> å¨ Palmer Dabbelt <palmer@dabbelt.com>ï¼2022å¹´5æ11æ¥ ä¸å5:59åéï¼
>
> On Thu, 05 May 2022 11:45:50 PDT (-0700), [1]gcc-patches@gcc.gnu.org
> wrote:
> > On Thu, May 05, 2022 at 06:33:20PM +0800, jiawei wrote:
> >> Some compiler target like arm-linux\riscv\power\s390x\xtensa-gcc
> handle
> >> char as unsigned char, then there are no warnings occur and got
> FAIL cases.
> >> Just change the type char into explicit signed char to keep the
> feature
> >> consistency.
> >>
> >> gcc/testsuite/ChangeLog:
> >>
> >>Â Â Â Â Â Â Â Â * c-c++-common/Wconversion-1.c: Update type.
> >
> > Ok, and sorry for introducing this problem!
> So this is OK for trunk? Happy to commit it if you'd like, just
> wanted
> to make sure as I'm not seeing it on trunk.
> >> ---
> >>Â gcc/testsuite/c-c++-common/Wconversion-1.c | 2 +-
> >>Â 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/gcc/testsuite/c-c++-common/Wconversion-1.c
> b/gcc/testsuite/c-c++-common/Wconversion-1.c
> >> index ed65918c70f..7053f6b5dbb 100644
> >> --- a/gcc/testsuite/c-c++-common/Wconversion-1.c
> >> +++ b/gcc/testsuite/c-c++-common/Wconversion-1.c
> >> @@ -10,5 +10,5 @@ void g()
> >>Â Â Â signed char sc = 300; /* { dg-warning "conversion from
> .int. to .signed char. changes value from .300. to .44." } */
> >>Â Â Â unsigned char uc = 300; /* { dg-warning "conversion from
> .int. to .unsigned char. changes value from .300. to .44." } */
> >>Â Â Â unsigned char uc2 = 300u; /* { dg-warning "conversion from
> .unsigned int. to .unsigned char. changes value from .300. to .44."
> } */
> >> -Â char c2 = (double)1.0 + 200; /* { dg-warning "overflow in
> conversion from .double. to .char. changes value from .2.01e\\+2. to
> .127." } */
> >> +Â signed char c2 = (double)1.0 + 200; /* { dg-warning "overflow
> in conversion from .double. to .signed char. changes value from
> .2.01e\\+2. to .127." } */
> >>Â }
> >> --
> >> 2.25.1
> >>
> >
> > Marek
>
> References
>
> 1. mailto:gcc-patches@gcc.gnu.org
next parent reply other threads:[~2022-05-12 4:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <k49kbomqqftfj10bjs7e8o7p.1652323041358@email.android.com>
2022-05-12 4:31 ` Palmer Dabbelt [this message]
2022-05-05 10:33 jiawei
2022-05-05 18:45 ` Marek Polacek
2022-05-10 21:58 ` Palmer Dabbelt
2022-05-10 23:57 ` Marek Polacek
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=mhng-29692201-be36-483a-800f-1f08c1243d72@palmer-mbp2014 \
--to=palmer@dabbelt.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@sifive.com \
--cc=wuwei2016@iscas.ac.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).