From: Khem Raj <raj.khem@gmail.com>
To: Jens Rehsack <rehsack@gmail.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] gcc: Avoid non-aligned access for ARM5e
Date: Thu, 8 Oct 2015 09:40:02 -0700 [thread overview]
Message-ID: <32B54709-BA87-45AC-BDC0-22604B6D3979@gmail.com> (raw)
In-Reply-To: <6BA567C8-0D8A-402A-B733-2E9DECFD9844@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
> On Oct 8, 2015, at 9:07 AM, Jens Rehsack <rehsack@gmail.com> wrote:
>
>
>> Am 08.10.2015 um 16:46 schrieb Khem Raj <raj.khem@gmail.com>:
>>
>>
>>> On Oct 8, 2015, at 7:33 AM, Jens Rehsack <rehsack@gmail.com> wrote:
>>>
>>>
>>> [Icedtee Ticket #2153] -- see http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2153
>>>
>>> This patch prevents gcc generate code on ARM5e accessing 64 bit values, because gcc doesn't ensure they're 64 bit aligned.
>>> Accessing a 64 bit value from a 32 bit alignment causes segmentation faults.
>>>
>>> Patch is taken from https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/gcc/0001-ARMv5-disable-LDRD-STRD.patch
>>
>> Can you try using -mfix-cortex-m3-ldrd, does that help ?
>
> Well, I have a marvel-kirkwood - I'll give it a shot but don't know whether it works at all.
>
>> The patch is a workaround to gcc, as it seems real problem is in defining instruction constraints
>> please open a gcc bug for this.
>
> Dunno whether I want to have all that stress. When neither ARCH linux guys did that nor Icedtea
> maintainers, how could I succeed there?
>
> Best I can do is (if -mfix-cortex-m3-ldrd doesn't help), keep it private. When -mfix-cortex-m3-ldrd
> helps, is adding it to ./meta/conf/machine/include/tune-arm926ejs.inc a sane approach?
This might be OK. Although I would like to see it fixed in right way in gcc, we don’t want to carry patches
that are not accepted upstream. We already have 60 odd patches and we should reduce them if possible.
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2015-10-08 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 14:33 [PATCH 2/2] gcc: Avoid non-aligned access for ARM5e Jens Rehsack
2015-10-08 14:46 ` Khem Raj
2015-10-08 16:07 ` Jens Rehsack
2015-10-08 16:40 ` Khem Raj [this message]
2015-10-12 16:01 ` Jens Rehsack
2015-10-12 16:32 ` Khem Raj
2015-10-12 17:54 ` Jens Rehsack
2015-10-13 11:45 ` Otavio Salvador
2015-10-13 12:07 ` Phil Blundell
2015-10-13 12:18 ` Otavio Salvador
2015-10-14 13:31 ` Phil Blundell
2015-10-13 16:49 ` Khem Raj
2015-10-13 20:52 ` Jens Rehsack
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=32B54709-BA87-45AC-BDC0-22604B6D3979@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=rehsack@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.