From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001344] Allow nc_test_slave for lwIP to compile for targets with 128KiB RAM.
Date: Tue, 27 Sep 2011 05:45:00 -0000 [thread overview]
Message-ID: <20110927054529.EA1F32F78001@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001344-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001344
--- Comment #3 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2011-09-27 06:45:27 BST ---
(In reply to comment #2)
> (In reply to comment #1)
> > (In reply to comment #0)
> > > Created an attachment (id=1377)
--> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1377) [details] Reduce
stack usage of
> > > nc_test_slave
>
> >
> > Hi Ilija,
> >
> > I have one **minor** remark regarding attachment 1377 [details]. I
> > would use ECHO_STACK_SIZE in the patch instead proposed name
> > (TMAIN_STACK_SIZE), IMO, such "adjusted" names would look nicer
>
> Thanks for comment Sergei.
>
> I selected stack names to reflect thread names. Regarding your
> proposal I assume that you mean MAIN_STACK_SIZE => ECHO_STACK_SIZE
> rather than TMAIN..., aren't you?
Hmm. I see
@@ -748,7 +750,7 @@
0, // entry parameter
"socket echo test", // Name
&stack[0], // Stack
- STACK_SIZE, // Size
+ TMAIN_STACK_SIZE, // Size
&thread_handle, // Handle
&thread_data // Thread data structure
);
So, I've meant s/TMAIN/ECHO/.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-09-27 5:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 7:28 [Bug 1001344] New: " bugzilla-daemon
2011-09-26 20:11 ` [Bug 1001344] " bugzilla-daemon
2011-09-26 21:30 ` bugzilla-daemon
2011-09-27 5:45 ` bugzilla-daemon [this message]
2011-09-27 7:35 ` bugzilla-daemon
2011-09-27 9:06 ` bugzilla-daemon
2011-10-02 14:36 ` bugzilla-daemon
2011-10-02 17:23 ` bugzilla-daemon
2011-10-02 17:29 ` bugzilla-daemon
2011-10-02 17:32 ` bugzilla-daemon
2011-10-02 17:36 ` bugzilla-daemon
2011-10-02 17:50 ` bugzilla-daemon
2011-10-02 19:06 ` bugzilla-daemon
2011-10-02 19:24 ` bugzilla-daemon
2012-05-13 10:50 ` bugzilla-daemon
2012-05-13 11:22 ` bugzilla-daemon
2012-05-14 20:36 ` bugzilla-daemon
2012-05-15 9:26 ` bugzilla-daemon
2012-05-15 9:55 ` bugzilla-daemon
2012-05-15 11:04 ` bugzilla-daemon
2012-05-16 0:28 ` bugzilla-daemon
2012-05-16 16:04 ` bugzilla-daemon
2012-05-16 16:20 ` bugzilla-daemon
2012-05-17 15:54 ` bugzilla-daemon
2012-05-17 16:12 ` bugzilla-daemon
2012-05-17 16:12 ` bugzilla-daemon
2012-05-17 17:04 ` bugzilla-daemon
2012-05-17 17:45 ` bugzilla-daemon
2012-05-18 7:25 ` bugzilla-daemon
2012-05-18 15:28 ` bugzilla-daemon
2012-05-26 19:19 ` bugzilla-daemon
2012-05-27 0:09 ` bugzilla-daemon
2012-05-27 8:32 ` bugzilla-daemon
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=20110927054529.EA1F32F78001@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@ecos.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).