From: "Moore, Catherine" <Catherine_Moore@mentor.com>
To: Petar Jovanovic <petar.jovanovic@rt-rk.com>,
'Matthew Fortune' <Matthew.Fortune@imgtec.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"'Maciej W. Rozycki'" <macro@linux-mips.org>
Cc: "Moore, Catherine" <Catherine_Moore@mentor.com>
Subject: RE: [PATCH v2][MIPS] fix CRT_CALL_STATIC_FUNCTION macro
Date: Fri, 13 Feb 2015 01:36:00 -0000 [thread overview]
Message-ID: <FD3DCEAC5B03E9408544A1E416F112420189153090@NA-MBX-04.mgc.mentorg.com> (raw)
In-Reply-To: <000201d04723$f69b1350$e3d139f0$@rt-rk.com>
> -----Original Message-----
> From: Petar Jovanovic [mailto:petar.jovanovic@rt-rk.com]
> Sent: Thursday, February 12, 2015 7:28 PM
> Subject: RE: [PATCH v2][MIPS] fix CRT_CALL_STATIC_FUNCTION macro
>
> -----Original Message-----
> From: Moore, Catherine [mailto:Catherine_Moore@mentor.com]
> Sent: Friday, February 6, 2015 4:13 PM
> To: Matthew Fortune; Petar Jovanovic; gcc-patches@gcc.gnu.org; 'Maciej W.
> Rozycki'
> Subject: RE: [PATCH v2][MIPS] fix CRT_CALL_STATIC_FUNCTION macro
>
>
> > Petar, would you please add your testcase to the gcc testsuite and repost
> the patch.
>
> Hi Catherine,
>
> Sure, I can repost the patch and add the test case I used.
> My concern - and I would appreciate feedback from you and others on it - is
> that the test I originally used to report [1] the problem creates a large
> executable (380 MB).
>
>
> The test also takes time to execute. Obviously, I can make it slightly more
> complex and make execute time short. Another path is to introduce and use
> options such as "Wl,-Ttext-segment" to make its size smaller. Any other
> ideas?
>
Hi Petar,
There isn't any need to execute a large testcase. Instead, try adding a short version of your test to the directory gcc/testsuite/gcc.target/mips.
There are examples of other tests there they check for specific assembler sequences by using scan-assembler. See umips-swp-1.c (and others) for a specific example of how to do this.
Let me know if you need additional help.
Thanks,
Catherine
next prev parent reply other threads:[~2015-02-13 1:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <003e01d04179$ccc38bc0$664aa340$@rt-rk.com>
2015-02-05 20:51 ` Matthew Fortune
2015-02-06 10:43 ` Maciej W. Rozycki
2015-02-06 10:57 ` Matthew Fortune
2015-02-06 12:23 ` Maciej W. Rozycki
2015-02-06 17:27 ` Mike Stump
2015-02-06 17:41 ` Matthew Fortune
2015-02-06 18:03 ` Mike Stump
2015-02-06 19:19 ` Maciej W. Rozycki
2015-02-06 17:46 ` Maciej W. Rozycki
2015-02-06 15:12 ` Moore, Catherine
2015-02-13 0:28 ` Petar Jovanovic
2015-02-13 1:36 ` Moore, Catherine [this message]
2015-04-16 16:53 ` Petar Jovanovic
2015-04-16 18:23 ` Maciej W. Rozycki
2015-04-16 20:38 ` Moore, Catherine
[not found] <6a22-55314b00-5-5cf51280@159592552>
2015-04-17 18:23 ` Petar Jovanovic
2015-04-17 18:35 ` Moore, Catherine
2015-04-21 18:05 ` Petar Jovanovic
2015-04-17 19:36 ` Maciej W. Rozycki
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=FD3DCEAC5B03E9408544A1E416F112420189153090@NA-MBX-04.mgc.mentorg.com \
--to=catherine_moore@mentor.com \
--cc=Matthew.Fortune@imgtec.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=macro@linux-mips.org \
--cc=petar.jovanovic@rt-rk.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 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).