Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: msnyder@sonic.net
Cc: gdb-patches@sourceware.org, gaius@glam.ac.uk
Subject: Re: [RFC] logic change in m2-valprint.c
Date: Sun, 01 Jul 2007 15:49:00 -0000	[thread overview]
Message-ID: <20070701154831.GE10872@caradoc.them.org> (raw)
In-Reply-To: <16087.12.7.175.2.1183076995.squirrel@webmail.sonic.net>

On Thu, Jun 28, 2007 at 05:29:55PM -0700, Michael Snyder wrote:
> I'm really not sure about this, call it a shot in the dark.
> 
> The logic doesn't make sense as it is (the condition can't be true),
> so I figured maybe the conditional had been reversed by mistake.
> 
> Either that, or the two lines should be removed, 'cause they're dead.
> 

> 2007-06-28  Michael Snyder  <msnyder@access-company.com>
> 
> 	* m2-valprint.c (m2_print_long_set): Logical condition reversed
> 	(Coverity).

It can't be backwards; this is trying to print "1" or "1, 2" but your
change would make it print ", 1" and ", 12".

I think it's also trying to shorten ranges to "{1..3, 6..7}".  The
bug's got to be in there somewhere.  Why's the code dead?  I'm not
seeing it... element_seen can be reset by the bit clear case, and then
we'll get into the test you're changing again.


-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-07-01 15:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29  0:37 msnyder
2007-07-01 15:49 ` Daniel Jacobowitz [this message]
2007-07-01 15:54   ` Michael Snyder
2007-07-01 16:03     ` Daniel Jacobowitz
2007-07-03  0:05       ` msnyder
2007-07-03  1:12         ` Daniel Jacobowitz
2007-07-03  1:21           ` msnyder
2007-07-03  1:24             ` Daniel Jacobowitz
2007-07-03  1:40               ` msnyder
2007-07-03  7:42           ` Mark Kettenis
2007-07-03 19:26             ` Jim Blandy

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=20070701154831.GE10872@caradoc.them.org \
    --to=drow@false.org \
    --cc=gaius@glam.ac.uk \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@sonic.net \
    /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