public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112112] Improper Arithmetic Type Conversion in s390x-linux-gnu-gcc
Date: Wed, 01 Nov 2023 09:16:26 +0000 [thread overview]
Message-ID: <bug-112112-4-qQUX3QwuRm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112112-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112112
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-11-01
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
--- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to 김대영 from comment #6)
> ```
> z3rodae0@z3rodae0:~$ ./sh.sh
> result for -O0 "signed" = 1
> result for -O1 "signed" = 1
> result for -O2 "signed" = 1
> result for -O3 "signed" = 1
> result for -O0 "unsigned" = 0
> result for -O1 "unsigned" = 0
> result for -O2 "unsigned" = 0
> result for -O3 "unsigned" = 0
> result for -O0 "" = 1
> result for -O1 "" = 1
> result for -O2 "" = 1
> result for -O3 "" = 1
> ```
>
> That's correct. I ran your code and script in my environment, and it
> produced the same results
That is weird.
I don't see a meaningful difference between the version without signed or
unsigned and your program, and you get inconsistent results with your
original program and consistent results with the other one.
Or am I missing something?
next prev parent reply other threads:[~2023-11-01 9:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 3:12 [Bug c/112112] New: " 22s302h0659 at sonline20 dot sen.go.kr
2023-10-28 3:22 ` [Bug c/112112] " 22s302h0659 at sonline20 dot sen.go.kr
2023-10-28 3:26 ` pinskia at gcc dot gnu.org
2023-10-28 6:20 ` pinskia at gcc dot gnu.org
2023-10-28 6:32 ` [Bug target/112112] " 22s302h0659 at sonline20 dot sen.go.kr
2023-10-29 9:06 ` tkoenig at gcc dot gnu.org
2023-10-31 2:32 ` 22s302h0659 at sonline20 dot sen.go.kr
2023-11-01 9:16 ` tkoenig at gcc dot gnu.org [this message]
2023-11-01 11:28 ` 22s302h0659 at sonline20 dot sen.go.kr
2023-11-10 10:24 ` 22s302h0659 at sonline20 dot sen.go.kr
2023-12-14 8:42 ` xry111 at gcc dot gnu.org
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=bug-112112-4-qQUX3QwuRm@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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 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).