From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb-patches@sourceware.org>
Subject: ARI troubles
Date: Tue, 24 Apr 2012 23:00:00 -0000 [thread overview]
Message-ID: <000001cd226b$40dfdb70$c29f9250$@muller@ics-cnrs.unistra.fr> (raw)
Hi all,
it's been a long time since I really looked at the ARI web page...
I wanted to remove the inline ARI rule as
discussed earlier on the list.
It degraded quite a lot recently:
http://sourceware.org/gdb/current/ari/
But most of the critical renentrant bugs are just
problems releated to introduction
of
common/common-utils.[ch]
My problem here is that the same gdb_ari.sh script
is used both for trunk as well as fixes branch...
How should I cope with such changes?
Pierre Muller
GDB pascal language maintainer
PS: Should I commit the change below
that effecitvely removed inline ARI rule?
Index: gdb_ari.sh
===================================================================
RCS file: /cvs/gdbadmin/ss/gdb_ari.sh,v
retrieving revision 1.110
diff -u -p -r1.110 gdb_ari.sh
--- gdb_ari.sh 30 May 2011 19:55:37 -0000 1.110
+++ gdb_ari.sh 24 Apr 2012 22:39:35 -0000
@@ -676,15 +676,16 @@ FNR == 1 {
}
}
-BEGIN { doc["inline"] = "\
-Do not use the inline attribute; \
-since the compiler generally ignores this, better algorithm selection \
-is needed to improved performance"
- category["inline"] = ari_code
-}
-/(^|[^_[:alnum:]])inline([^_[:alnum:]]|$)/ {
- fail("inline")
-}
+# Commented out, but left inside sources, just in case.
+# BEGIN { doc["inline"] = "\
+# Do not use the inline attribute; \
+# since the compiler generally ignores this, better algorithm selection \
+# is needed to improved performance"
+# category["inline"] = ari_code
+# }
+# /(^|[^_[:alnum:]])inline([^_[:alnum:]]|$)/ {
+# fail("inline")
+# }
# This test is obsolete as this type
# has been deprecated and finally suppressed from GDB sources
cvs diff: Diffing CVSROOT
next reply other threads:[~2012-04-24 22:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 23:00 Pierre Muller [this message]
[not found] <4f972bf9.44d8b60a.1aeb.73dcSMTPIN_ADDED@mx.google.com>
2012-04-25 1:06 ` Pedro Alves
2012-04-25 16:11 ` Joel Brobecker
2012-04-25 16:14 ` Pierre Muller
[not found] ` <4f98223f.094ab60a.6b23.1692SMTPIN_ADDED@mx.google.com>
2012-04-25 16:56 ` Doug Evans
2012-04-25 17:02 ` Joel Brobecker
2012-04-26 15:43 ` Doug Evans
2012-04-26 16:02 ` Pierre Muller
2012-04-26 16:31 ` Joel Brobecker
2012-04-30 17:26 ` Jan Kratochvil
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='000001cd226b$40dfdb70$c29f9250$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--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