public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom de Vries <Tom_deVries@mentor.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Jakub Jelinek <jakub@redhat.com>,
	Rainer Orth	<ro@CeBiTec.Uni-Bielefeld.DE>,
	Mike Stump <mikestump@comcast.net>
Subject: [RFC] Dejagnu patch to handle multi-line directives
Date: Sat, 10 Jun 2017 07:57:00 -0000	[thread overview]
Message-ID: <b096fda2-5ed8-f8c1-ddd0-4ee1bb7f8565@mentor.com> (raw)

Hi,

one thing that has bothered me on a regular basis is the inability to 
spread long dejagnu directives over multiple lines.

I've written a demonstrator patch (for the dejagnu sources) and tested 
it by splitting this 108 chars line:
...
/* { dg-additional-options "-DSTACK_SIZE=[dg-effective-target-value 
stack_size]" { target { stack_size } } } */
...
into:
...
/* { dg-additional-options }
    { dg-dc "-DSTACK_SIZE=[dg-effective-target-value stack_size]" }
    { dg-dc { target { stack_size } } } */
...

Good idea to fix this?

Good idea to fix this like this?

If so, any other comments, before I suggest this at dejagnu project?

Thanks,
- Tom

             reply	other threads:[~2017-06-10  7:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-10  7:57 Tom de Vries [this message]
2017-06-10  8:03 ` Tom de Vries
2017-06-11  0:42   ` Segher Boessenkool
2017-06-12  7:59   ` Richard Sandiford
2017-06-12 18:54     ` Pedro Alves
2017-06-13  6:59       ` Richard Sandiford
2017-06-12 16:58 ` Mike Stump
2017-06-20 13:28   ` Rainer Orth

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=b096fda2-5ed8-f8c1-ddd0-4ee1bb7f8565@mentor.com \
    --to=tom_devries@mentor.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=mikestump@comcast.net \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).