public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Ian Lance Taylor <ian@airs.com>
Cc: "Kaveh R. Ghazi" <ghazi@caipclassic.rutgers.edu>,
	 gcc@gcc.gnu.org,  joseph@codesourcery.com
Subject: Re: [PATCH]: Proof-of-concept for dynamic format checking
Date: Wed, 17 Aug 2005 20:25:00 -0000	[thread overview]
Message-ID: <87acjg2tww.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <m364u48hb9.fsf@gossamer.airs.com> (Ian Lance Taylor's message of "17 Aug 2005 13:00:26 -0700")

* Ian Lance Taylor:

> Florian Weimer <fw@deneb.enyo.de> writes:
>
>> If I understand your %A/%B example correctly, it would look like this:
>
> OK, I can see how that might work in a simple case.  Now, can you give
> me an example of matching %d with the various flags?  In particular,
> are you going to write a loop, and is gcc going to somehow fully
> unroll that loop at compile time?

This is indeed a problem (with GCC 4.0 at least).  A regexp builtin
which returns the length of the matched string probably could probably
solve this.  Managing state so that you can still compose multiple
checkers is the harder part, I think.

  reply	other threads:[~2005-08-17 20:25 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200508111509.j7BF9qMq015700@caipclassic.rutgers.edu>
2005-08-17 19:15 ` Ian Lance Taylor
2005-08-17 19:19   ` Florian Weimer
2005-08-17 19:25     ` Ian Lance Taylor
2005-08-17 19:45       ` Florian Weimer
2005-08-17 20:00         ` Ian Lance Taylor
2005-08-17 20:25           ` Florian Weimer [this message]
2005-08-17 19:25     ` Mike Stump
2005-08-18  1:00     ` Giovanni Bajo
2005-08-18  1:20       ` Ian Lance Taylor
2005-08-18 11:56         ` Dave Korn
2005-08-18 12:00           ` Florian Weimer
2005-08-18 12:09             ` Dave Korn
2005-08-18 19:10               ` Mike Stump
2005-08-18 19:54                 ` Branko Čibej
2005-08-18 21:52                   ` Vincent Lefevre
2005-08-19  0:54                     ` Joe Buck
2005-08-19  1:34                       ` James E Wilson
2005-08-19  2:23                         ` Robert Dewar
2005-08-19 10:32                       ` Vincent Lefevre
2005-08-18 22:51                   ` Mike Stump
2005-08-18 12:00       ` Florian Weimer
2005-08-18 16:38         ` Ian Lance Taylor
2005-08-19 19:40   ` Tom Tromey
2005-08-19 20:28     ` Internal Behavior of G++ Aoun Raza
2005-08-19 20:30       ` Joe Buck
2005-08-19 20:57         ` Aoun Raza
2005-08-19 21:11           ` Mike Stump
2005-08-19 21:17     ` [PATCH]: Proof-of-concept for dynamic format checking Ian Lance Taylor
2005-08-28 21:17       ` Daniel Jacobowitz
2005-08-28 23:28         ` Ken Raeburn
2005-08-18  2:01 ` Kaveh R. Ghazi
2005-08-18  2:08   ` Kaveh R. Ghazi
2005-08-18  2:50     ` Ian Lance Taylor
2005-08-18  3:07       ` Kaveh R. Ghazi
2005-08-18  3:42         ` Alan Modra
2005-08-18 12:46           ` Kaveh R. Ghazi
2005-08-18 13:41             ` Alan Modra
2005-08-18 14:35               ` Kaveh R. Ghazi
2005-08-19  1:08                 ` Alan Modra
2005-08-19  2:56                   ` Ian Lance Taylor

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=87acjg2tww.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=gcc@gcc.gnu.org \
    --cc=ghazi@caipclassic.rutgers.edu \
    --cc=ian@airs.com \
    --cc=joseph@codesourcery.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).