From: Kwok Cheung Yeung <kcy@codesourcery.com>
To: <amodra@gmail.com>
Cc: <binutils@sourceware.org>
Subject: Re: powerpc-vxworks testers needed
Date: Thu, 27 Mar 2014 12:40:00 -0000 [thread overview]
Message-ID: <53341AEA.7060707@codesourcery.com> (raw)
> Now, I don't have access to a powerpc-vxworks system, so this patch
> might leave vxworks broken due to additional features being enabled.
> For example, TLS optimisation will now occur on powerpc-vxworks, and
> I don't have any information on how TLS is implemented on vxworks.
> Hopefully, it follows my original ppc tls implementation in terms of
> code and reloc sequences.. If not, I'd like to hear about problems
> now rather than a week or so after the next binutils release. ;)
I have backported your patches for the PPC476 workaround to an older
version of binutils (a snapshot of 2.19, dating from around the middle
of 2009). Automated Dejagnu testing shows no noticeable regressions on
PowerPC VxWorks.
Regards
Kwok Yeung
next reply other threads:[~2014-03-27 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 12:40 Kwok Cheung Yeung [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-27 13:08 Alan Modra
2014-03-03 19:07 ` Jerome Guitton
2014-03-03 23:20 ` Alan Modra
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=53341AEA.7060707@codesourcery.com \
--to=kcy@codesourcery.com \
--cc=amodra@gmail.com \
--cc=binutils@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).