public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/1278] regex undefined behavior with shifting past word length Date: Thu, 01 Sep 2005 22:29:00 -0000 [thread overview] Message-ID: <20050901222930.21697.qmail@sourceware.org> (raw) In-Reply-To: <20050831193645.1278.eggert@gnu.org> ------- Additional Comments From eggert at gnu dot org 2005-09-01 22:29 ------- The last hunk is purely for ports to ones' complement and signed-magnitude hosts. It has no effect in the normal case. For example, on a one's complement host, ~0 has the numeric value zero, i.e., ~0 == 0. Also, ~0 is of type int. When ~0 is converted to unsigned int, it is converted by value, not by bit-pattern. (The C Standard requires this.) Hence ((unsigned) ~0) is equivalent to ((unsigned) 0), which in turn is equivalent to 0u, which is zero. The same problem occurs with signed-magnitude hosts. It also occurs with unsigned short int (the type being used here). Admittedly this is a minor point since such hosts are rare, but it's easy to do portably so we might as well do it that way. -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=1278 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-09-01 22:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-31 19:37 [Bug regex/1278] New: " eggert at gnu dot org 2005-08-31 19:37 ` [Bug regex/1278] " eggert at gnu dot org 2005-09-01 7:04 ` paolo dot bonzini at lu dot unisi dot ch 2005-09-01 10:00 ` schwab at suse dot de 2005-09-01 22:29 ` eggert at gnu dot org [this message] 2005-09-02 6:17 ` paolo dot bonzini at lu dot unisi dot ch 2005-09-02 10:21 ` schwab at suse dot de 2005-09-02 23:17 ` eggert at gnu dot org 2005-09-06 7:32 ` eggert at gnu dot org 2005-09-06 23:30 ` drepper at redhat dot com
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=20050901222930.21697.qmail@sourceware.org \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs-regex@sources.redhat.com \ /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: linkBe 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).