From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Petar Jovanovic <petar.jovanovic@rt-rk.com>
Cc: gcc-patches@gcc.gnu.org, Catherine_Moore@mentor.com,
Matthew.Fortune@imgtec.com
Subject: Re: [PATCH v3][MIPS] fix CRT_CALL_STATIC_FUNCTION macro
Date: Tue, 21 Apr 2015 18:52:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.11.1504211940450.4047@eddie.linux-mips.org> (raw)
In-Reply-To: <005001d07c5a$8c9e9b90$a5dbd2b0$@rt-rk.com>
On Tue, 21 Apr 2015, Petar Jovanovic wrote:
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/mips/call-from-init.c
> @@ -0,0 +1,10 @@
> +/* Check that __do_global_ctors_aux can be reached from .init section that
> + is in a different (256MB) region. */
> +/* { dg-do run } */
> +/* { dg-options "-Wl,--section-start=.init=0x0FF00000" } */
> +/* { dg-options "-Wl,--section-start=.text=0x10000000" } */
Hmm, the addresses should work for any virtual-memory targets, however if
this is going to be a run-time test, then not for bare-iron ones, as they
won't normally support mapped addresses. And we may not be able to come
up with better ones, because a typical bare-iron target will often not
have enough memory to span a 256MB boundary. I think this will best be
reduced to a link-only test on bare iron, hoping for a link failure.
Speaking of which, have you been able to make a linker test case out of
this example for a bug report against binutils? Not necessarily a proper
LD test suite addition, I wouldn't be asking for *that*! Just a small
case will do, e.g. a pair of .s files generated out of this source and the
generated crtbegin.s file, preferably with unrelated clutter removed,
together with a recipe how to assemble them and link to show the missing
error message. That will certainly help covering this issue all and for
good!
Thanks,
Maciej
next prev parent reply other threads:[~2015-04-21 18:52 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 [this message]
2015-04-22 15:42 ` Petar Jovanovic
2015-04-23 14:55 ` Maciej W. Rozycki
2015-04-24 15:13 ` Petar Jovanovic
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=alpine.LFD.2.11.1504211940450.4047@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=Catherine_Moore@mentor.com \
--cc=Matthew.Fortune@imgtec.com \
--cc=gcc-patches@gcc.gnu.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).