All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Rehsack <rehsack@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>,
	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: Tue, 13 Oct 2015 22:52:44 +0200	[thread overview]
Message-ID: <263EC7D2-E003-4C72-B2CE-167C37C00FF6@gmail.com> (raw)
In-Reply-To: <669CD3FB-176B-4FA7-A944-5C96F19FB381@gmail.com>


> Am 13.10.2015 um 18:49 schrieb Khem Raj <raj.khem@gmail.com>:
> 
>> 
>> On Oct 13, 2015, at 4:45 AM, Otavio Salvador <otavio.salvador@ossystems.com.br> wrote:
>> 
>> Hello Jens and Khem,
>> 
>> On Mon, Oct 12, 2015 at 2:54 PM, Jens Rehsack <rehsack@gmail.com> wrote:
>>>> Am 12.10.2015 um 18:32 schrieb Khem Raj <raj.khem@gmail.com>:
>>>> On Mon, Oct 12, 2015 at 9:01 AM, Jens Rehsack <rehsack@gmail.com> wrote:
>>>>>> Am 08.10.2015 um 18:40 schrieb Khem Raj <raj.khem@gmail.com>:
>>>>> [...]
>>>>> During hacking on the fix in meta/conf/machine/ I recognized that the expected thump suffix in meta/conf/machine/include/tune-arm926ejs.inc
>>>>> isn't there and modified the line as
>>>>> 
>>>>> diff --git a/meta/conf/machine/include/tune-arm926ejs.inc b/meta/conf/machine/include/tune-arm926ejs.inc
>>>>> index 335e4e0..a310c9d 100644
>>>>> --- a/meta/conf/machine/include/tune-arm926ejs.inc
>>>>> +++ b/meta/conf/machine/include/tune-arm926ejs.inc
>>>>> @@ -8,4 +8,4 @@ TUNE_CCARGS .= "${@bb.utils.contains("TUNE_FEATURES", "arm926ejs", " -mtune=arm9
>>>>> AVAILTUNES += "arm926ejs"
>>>>> ARMPKGARCH_tune-arm926ejs = "arm926ejs"
>>>>> TUNE_FEATURES_tune-arm926ejs = "${TUNE_FEATURES_tune-armv5te} arm926ejs"
>>>>> -PACKAGE_EXTRA_ARCHS_tune-arm926ejs = "${PACKAGE_EXTRA_ARCHS_tune-armv5te} arm926ejste"
>>>>> +PACKAGE_EXTRA_ARCHS_tune-arm926ejs = "${PACKAGE_EXTRA_ARCHS_tune-armv5te} arm926ejste arm926ejse"
>>>>> 
>>>> 
>>>> this is ok ?
>>> 
>>> From
>>> 
>>> TUNE_FEATURES="${TUNE_FEATURES_tune-${DEFAULTTUNE}}"
>>> 
>>> is ok probably the wrong question ;)
>>> 
>>> Setting DEFAULTTUNE to arm926ejs results in expanding PACKAGE_ARCH from TUNE_PKGARCH which is combined via
>>> "${ARMPKGARCH}${ARMPKGSFX_THUMB}${ARMPKGSFX_DSP}${ARMPKGSFX_EABI}${ARMPKGSFX_ENDIAN}${ARMPKGSFX_FPU}" in
>>> meta/conf/machine/include/arm/arch-arm.inc:12
>>> 
>>> Since ARMPKGSFX_THUMB is set to "t" (or "t2" on ARMv6+) only when thumb code should be generated and
>>> ARMPKGSFX_DSP is set to "e" when DSP is featured, both have to be recognized.
>>> 
>>> The entire construct doesn't feel "ok'ish" - but it works and is more or less reliable ...
>> 
>> I understand Khem is excitant to include more non-upstreamed patches
>> into GCC but I would prefer to have it included and Java working fine
>> than a local patch applied forever. :-(
> 
> All I am asking is to open a bug with gcc. So to get some opinion on impact of patch, workaround of this nature can
> be degarading code generation, we do not have any report on that. So that my concern was

I will check how difficult it is and report if it's a low hangin' fruit ;)

Cheers
-- 
Jens Rehsack - rehsack@gmail.com



      reply	other threads:[~2015-10-13 20:52 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
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 [this message]

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=263EC7D2-E003-4C72-B2CE-167C37C00FF6@gmail.com \
    --to=rehsack@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=otavio@ossystems.com.br \
    --cc=raj.khem@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.