Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] bitpos expansion summary reloaded
Date: Tue, 23 Oct 2012 19:11:00 -0000	[thread overview]
Message-ID: <20121023191049.GA17307@host2.jankratochvil.net> (raw)
In-Reply-To: <20121021130546.02ea680c@spoyarek>

Hi Siddhesh,

in the mail
	http://sourceware.org/ml/gdb-patches/2012-09/msg00706.html

I have reported bitpos-patched GDB has the problem on line ada-valprint.c:700.

I do see this incomplete extension neither fixed nor listed in the
gcc-warnings.out.report file.

I see why, the line had the -Wconversion warning even before so it correctly
did not appear in the .report.  But there is missing a bitpos extension now.

When I run -Wconversion by hand I do get:
	ada-valprint.c: In function ‘ada_val_print_1’:
	ada-valprint.c:700:68: error: conversion to ‘int’ from ‘long int’ may alter its value [-Werror=conversion]
while on the unpatched source tree one gets:
	ada-valprint.c: In function ‘ada_val_print_1’:
	ada-valprint.c:699:68: error: conversion to ‘int’ from ‘long int’ may alter its value [-Werror=conversion]

Unless one carefully checks all the uses of any extended variable - which
I was doing occasionally by hand but I understand it is very fragile to do in
all the cases by hand - this method does not work.

So there are these options:

(1) Check in the patchset as is while it is known not all type safety
    regressions have been caught.

(2) Fix all -Wconversion warnings, either by cast or by type extension,
    depending on the case.  But this can be done anytime later.

The whole review effort improved the quality of (1) but it is still not a 100%
fix.

Fortunately (2) can be done in parts, (1) could not have been done in parts as
one cannot separate former -Wconversion vs. latter -Wconversion messages. But
it has been shown (1) cannot be done perfectly without (2).



Regards,
Jan


  parent reply	other threads:[~2012-10-23 19:11 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27 13:33 Siddhesh Poyarekar
2012-09-28 11:20 ` Jan Kratochvil
2012-09-28 11:40   ` Siddhesh Poyarekar
2012-09-28 12:06     ` Jan Kratochvil
2012-09-28 12:19       ` Siddhesh Poyarekar
2012-09-29 17:39 ` Jan Kratochvil
2012-09-29 18:12   ` Jan Kratochvil
2012-09-30  6:52     ` Jan Kratochvil
2012-10-01  5:21       ` Siddhesh Poyarekar
2012-10-01  6:14         ` Jan Kratochvil
2012-10-03 13:12       ` Siddhesh Poyarekar
2012-10-03 18:38         ` Jan Kratochvil
2012-10-04  7:20           ` Siddhesh Poyarekar
2012-10-03 19:56         ` Jan Kratochvil
2012-10-04  7:13           ` Jan Kratochvil
2012-10-21  7:36             ` Siddhesh Poyarekar
2012-10-22 20:45               ` Tom Tromey
2012-10-23  1:34                 ` Jan Kratochvil
2012-10-23  1:58                   ` Jan Kratochvil
2012-10-23  2:29                     ` Siddhesh Poyarekar
2012-10-23  2:37                       ` Jan Kratochvil
2012-10-23  2:38                   ` Tom Tromey
2012-10-23 19:11               ` Jan Kratochvil [this message]
2012-10-24 18:33                 ` Tom Tromey
2012-10-24 18:55                   ` Jan Kratochvil
2012-10-24 20:18                     ` Tom Tromey
2012-10-25 15:54               ` Jan Kratochvil
2012-10-25 16:52                 ` Siddhesh Poyarekar
2012-11-06 20:01                   ` Jan Kratochvil
2012-11-07 13:48                     ` Jan Kratochvil
2012-11-13 19:46                       ` Tom Tromey
2012-11-13 19:55                         ` Jan Kratochvil
2012-11-01 15:24               ` Jan Kratochvil
2012-11-01 16:56                 ` Siddhesh Poyarekar

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=20121023191049.GA17307@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=siddhesh@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