From: Mike Stump <mikestump@comcast.net>
To: Tom de Vries <Tom_deVries@mentor.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Subject: Re: Add dg-add-options feature stack_size
Date: Mon, 19 Jun 2017 17:36:00 -0000 [thread overview]
Message-ID: <B50CB12D-A928-4D41-9C6F-4CEB9E602D8E@comcast.net> (raw)
In-Reply-To: <bfa700c2-db7a-e39a-6de9-4100ab777b01@mentor.com>
On Jun 19, 2017, at 10:11 AM, Tom de Vries <Tom_deVries@mentor.com> wrote:
>
> I came across dg-add-options, and wondered if adding a dg-add-options feature stack_size is a better way to make STACK_SIZE available.
I don't have a strong opinion here, but, it does look a tad simpler and nicer.
> OK if complete and tested?
Ok.
next prev parent reply other threads:[~2017-06-19 17:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 14:24 [PATCH, testsuite] Add effective target stack_size Tom de Vries
2017-06-09 15:25 ` Mike Stump
2017-06-12 12:28 ` Christophe Lyon
2017-06-12 14:29 ` Tom de Vries
2017-06-19 9:21 ` Christophe Lyon
2017-06-19 15:42 ` Mike Stump
2017-06-19 17:11 ` Add dg-add-options feature stack_size Tom de Vries
2017-06-19 17:36 ` Mike Stump [this message]
2017-06-21 13:19 ` [PATCH, testsuite] Add effective target stack_size Jakub Jelinek
2017-06-21 14:27 ` [testsuite, committed] Support dg-add-options in profopt.exp Tom de Vries
2022-11-08 20:29 ` nvptx: stack size limits are relevant for execution only (was: [PATCH, testsuite] Add effective target stack_size) Thomas Schwinge
2022-11-25 11:09 ` [PING] " Thomas Schwinge
2022-12-20 7:55 ` [PING^2] " Thomas Schwinge
2023-01-11 11:45 ` [PING^3] " Thomas Schwinge
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=B50CB12D-A928-4D41-9C6F-4CEB9E602D8E@comcast.net \
--to=mikestump@comcast.net \
--cc=Tom_deVries@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--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).