From: "Petar Jovanovic" <petar.jovanovic@rt-rk.com>
To: "'Maciej W. Rozycki'" <macro@linux-mips.org>
Cc: <gcc-patches@gcc.gnu.org>, <Catherine_Moore@mentor.com>,
"'Matthew Fortune'" <Matthew.Fortune@imgtec.com>
Subject: RE: [PATCH v3][MIPS] fix CRT_CALL_STATIC_FUNCTION macro
Date: Fri, 24 Apr 2015 15:13:00 -0000 [thread overview]
Message-ID: <003501d07ea1$29c7d1a0$7d5774e0$@rt-rk.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1504231508040.5204@eddie.linux-mips.org>
-----Original Message-----
From: Maciej W. Rozycki [mailto:macro@linux-mips.org]
Sent: Thursday, April 23, 2015 4:55 PM
To: Petar Jovanovic
Cc: gcc-patches@gcc.gnu.org; Catherine_Moore@mentor.com; Matthew Fortune
Subject: RE: [PATCH v3][MIPS] fix CRT_CALL_STATIC_FUNCTION macro
> I hope you find this explanation satisfactory, however if you still find
> anything unclear or have any other questions or concerns, then please
> shout.
Hi Maciej,
Thank you for your response. I should have coined my question better
though, so you do not need to write it all. In the v4 patch, I have
skipped the test for bare iron targets.
> BTW, can you please change 0x0FF00000 to 0x0FFF0000 or suchlike to avoid
> making the executable larger than absolutely necessary
Done.
> You didn't mention in your patch description why you picked up these
particular addresses.
There is a comment in the test which indicates that. I have put it as
part of the commit message now as well.
Regards,
Petar
prev parent reply other threads:[~2015-04-24 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 17:42 Petar Jovanovic
2015-04-21 18:52 ` Maciej W. Rozycki
2015-04-22 15:42 ` Petar Jovanovic
2015-04-23 14:55 ` Maciej W. Rozycki
2015-04-24 15:13 ` Petar Jovanovic [this message]
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='003501d07ea1$29c7d1a0$7d5774e0$@rt-rk.com' \
--to=petar.jovanovic@rt-rk.com \
--cc=Catherine_Moore@mentor.com \
--cc=Matthew.Fortune@imgtec.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=macro@linux-mips.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).