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/1217] New: regcomp.c elicits uninitialized-variable warnings with GCC 4
Date: Sat, 20 Aug 2005 00:05:00 -0000	[thread overview]
Message-ID: <20050820000542.1217.eggert@gnu.org> (raw)

regcomp.c contains code that elicits uninitialized-variable warnings with
GCC 4.  The problem is that GCC isn't smart enough to see that when
duplicate_node returns REG_ESPACE, the uninitialized storage is not used.
I'll attach a straightforward patch that changes the signature of
duplicate_node to avoid the warnings.  My impression is that the
patch also causes GCC to generate better code, but I haven't measured
this.

-- 
           Summary: regcomp.c elicits uninitialized-variable warnings with
                    GCC 4
           Product: glibc
           Version: 2.3.5
            Status: NEW
          Severity: minor
          Priority: P2
         Component: regex
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: eggert at gnu dot org
                CC: glibc-bugs-regex at sources dot redhat dot com,glibc-
                    bugs at sources dot redhat dot com


http://sources.redhat.com/bugzilla/show_bug.cgi?id=1217

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2005-08-20  0:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-20  0:05 eggert at gnu dot org [this message]
2005-08-20  0:06 ` [Bug regex/1217] " eggert at gnu dot org
2005-08-20  7:28 ` eggert at gnu dot org
2005-09-06 18:04 ` 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=20050820000542.1217.eggert@gnu.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: 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).