From: Renato Golin <renato.golin@linaro.org>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Saleem Abdulrasool <compnerd@compnerd.org>,
GCC Mailing List <gcc@gcc.gnu.org>,
Richard Sandiford <rsandifo@linux.vnet.ibm.com>
Subject: Re: ARM inline assembly usage in Linux kernel
Date: Wed, 19 Feb 2014 23:26:00 -0000 [thread overview]
Message-ID: <CAMSE1kcN9m_Wp-cCA_UfPJBeSkJwkHPqVv0CjjKCa4hwuF_GTQ@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1=hk63Fna77h1aWypaZt=p+u-4XzuO303=aWOZri=5Tsw@mail.gmail.com>
On 19 February 2014 23:19, Andrew Pinski <pinskia@gmail.com> wrote:
> With the unified assembly format, you should not need those
> .arm/.thumb and in fact emitting them can make things even worse.
If only we could get rid or all pre-UAL inline assembly on the planet... :)
The has been the only reason why we added support for those in our
assembler, because GAS supports them and people still use (or have
legacy code they won't change).
If the binutils folks (and you guys) are happy to start seriously
de-phasing pre-UAL support, I'd be more than happy to do so on our
end. Do you think I should start that conversation on the binutils
list?
Maybe a new serious compulsory warning, to start?
cheers,
--renato
next prev parent reply other threads:[~2014-02-19 23:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 2:56 Saleem Abdulrasool
2014-02-19 3:02 ` Andrew Pinski
2014-02-19 11:58 ` Richard Sandiford
2014-02-19 23:17 ` Renato Golin
2014-02-19 23:20 ` Andrew Pinski
2014-02-19 23:26 ` Renato Golin [this message]
2014-02-20 12:59 ` Ramana Radhakrishnan
2014-02-20 13:17 ` Renato Golin
2014-02-20 10:11 ` Ramana Radhakrishnan
2014-02-20 10:21 ` Renato Golin
2014-02-20 12:09 ` Richard Earnshaw
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=CAMSE1kcN9m_Wp-cCA_UfPJBeSkJwkHPqVv0CjjKCa4hwuF_GTQ@mail.gmail.com \
--to=renato.golin@linaro.org \
--cc=compnerd@compnerd.org \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@gmail.com \
--cc=rsandifo@linux.vnet.ibm.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).