Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] Send new ARI warnings to gdb_testers mailing list
Date: Thu, 08 Oct 2009 11:15:00 -0000	[thread overview]
Message-ID: <003401ca4808$96fd2070$c4f76150$@u-strasbg.fr> (raw)
In-Reply-To: <20090520052257.GB16152@adacore.com>

  Hi, 
sorry for answering so late on this email.

  Joel, do you still agree on 
moving the email-to address to gdb-testers?


> -----Message d'origine-----
> De : Joel Brobecker [mailto:brobecker@adacore.com]
> Envoyé : Wednesday, May 20, 2009 7:23 AM
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFC] Send new ARI warnings to gdb_testers mailing list
> 
> FWIW:
> 
> > >>>>>>>>>> Email Title
> > ARI warning list change Tue May 19 01:55:11 UTC 2009
> > >>>>>>>>>> Start of email body
> > 1049a1046,1047
> > > gdb/lm32-tdep.c:293: deprecate: write_memory: Replace
> write_memory() with
> > regcache_read() et.al.
> > > gdb/lm32-tdep.c:337: deprecate: read_memory: Replace read_memory()
> with
> > regcache_read() et.al.
> > 58,59d57
> > < gdb/doublest.h:96: deprecated: deprecated extract_floating: Do not
> use
> > deprecated extract_floating, see declaration for details
> > < gdb/doublest.h:97: deprecated: deprecated store_floating: Do not
> use
> > deprecated store_floating, see declaration for details
> > 106d103
> > < gdb/ada-lang.c:1695: deprecated: deprecated set_value_type: Do not
> use
> > deprecated set_value_type, see declaration for details
> > 163d159
> > < gdb/sh64-tdep.c:1580: deprecated: deprecated extract_floating: Do
> not use
> > deprecated extract_floating, see declaration for details
> > 1600,1601d1597
> > < gdb/doublest.c:822: deprecated: deprecated extract_floating: Do not
> use
> > deprecated extract_floating, see declaration for details
> > < gdb/doublest.c:839: deprecated: deprecated store_floating: Do not
> use
> > deprecated store_floating, see declaration for details
> > >>>>>>>>>> End of email
> 
> Can we just get the lines that start with "> "? As far as I can tell,
> we don't really need the "< " lines, since these are good news.
> The hunk headers (eg: 1600,1601d1597) are not really useful either.

  I have to disagree here:
In some cases, the new warning might just be due to
a change of the ordering of the source (for instance if you
move a function). In such a case, you would
be able to understand that it is not a really new
warning, but a displaced by looking at the

> > Should I change the email address to gdb-testers?
> 
> I would personally be OK with that; and I even think that this would
> be useful if all we were sending is the new regressions. Having
> the line number where the regression appeared is great.

Pierre


  reply	other threads:[~2009-10-08 11:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 22:10 Pierre Muller
2009-04-23 18:42 ` Joel Brobecker
2009-05-01  9:24   ` Pierre Muller
2009-05-06 16:31     ` Joel Brobecker
2009-05-06 16:46       ` Pierre Muller
2009-05-19  8:35         ` Pierre Muller
2009-05-20  5:23           ` Joel Brobecker
2009-10-08 11:15             ` Pierre Muller [this message]
2009-10-08 15:52               ` Joel Brobecker

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='003401ca4808$96fd2070$c4f76150$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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