public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dberlin@sources.redhat.com
To: dash@xdr.com, dberlin@sources.redhat.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: optimization/5969: When function is declared func(unsigned char v), v isn't truncated
Date: Sat, 16 Mar 2002 15:01:00 -0000	[thread overview]
Message-ID: <20020316230156.13845.qmail@sources.redhat.com> (raw)

Synopsis: When function is declared func(unsigned char v), v isn't truncated

Responsible-Changed-From-To: unassigned->dberlin
Responsible-Changed-By: dberlin
Responsible-Changed-When: Sat Mar 16 15:01:56 2002
Responsible-Changed-Why:
    Me
State-Changed-From-To: open->feedback
State-Changed-By: dberlin
State-Changed-When: Sat Mar 16 15:01:56 2002
State-Changed-Why:
    You have implicitly declared tst to take an int by using it before it's defined.
    Because it is inlined into main at -O2, and at that point it thinks it takes an int, it never performs the truncation.
    
    Any code after the tst function is defined to take an unsigned char will do the truncation.
    
    The problem is the code, not the compiler, AFAIK.
    The title of the bug report is misleading, you haven't declared func(unsigned char v), if you did, the problem would go away.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5969


             reply	other threads:[~2002-03-16 23:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-16 15:01 dberlin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-28 14:42 sirl
2002-03-16 16:16 David Ashley
2002-03-14 15:46 dash

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=20020316230156.13845.qmail@sources.redhat.com \
    --to=dberlin@sources.redhat.com \
    --cc=dash@xdr.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).