From: Mike Frysinger <vapier@gentoo.org>
To: ltp-list@lists.sourceforge.net, yanegomi@gmail.com
Cc: Markos Chandras <Markos.Chandras@imgtec.com>
Subject: Re: [LTP] [PATCH 03/21] test.h/tst_brkm: Drop __attribute__((noreturn)) since tst_brk can return to caller
Date: Tue, 3 Jan 2012 13:56:10 -0500 [thread overview]
Message-ID: <201201031356.11319.vapier@gentoo.org> (raw)
In-Reply-To: <4F02CC46.9000106@imgtec.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 481 bytes --]
On Tuesday 03 January 2012 04:37:10 Markos Chandras wrote:
> Hi, please review the attached patch
the tst_brk() API has gotten annoying. it is designed to not return to the
original caller which is why it had the "noreturn" attribute. but Garret re-
rewrote it to be re-entrant presumably so the cleanup() func could itself call
tst_brk(). but i'm not sure how useful that actually is in practice ...
Garret: could you comment on the actual use cases here ?
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 355 bytes --]
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-01-03 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 9:37 [LTP] [PATCH 03/21] test.h/tst_brkm: Drop __attribute__((noreturn)) since tst_brk can return to caller Markos Chandras
2012-01-03 18:56 ` Mike Frysinger [this message]
2012-01-04 13:46 ` Cyril Hrubis
[not found] ` <CAGH67wRsHvHkdvPrC5y4Fm7TuYxs1dHytJnnK3d54PxG-vukYA@mail.gmail.com>
2012-01-04 17:05 ` Cyril Hrubis
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=201201031356.11319.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=Markos.Chandras@imgtec.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.