A few more comments...
The MAP_DATA support is emitting mapping symbols documented in the
AARCH64 ELF ABI. Mapping symbols are emitted when switching from data
to instructions, or vice versa, inside a section. However, mapping
symbols are just addresses. There should be no need to emit implicit
On Tue, Jun 14, 2016 at 12:43 PM, Jim Wilson wrote:
> I can reproduce with an FSF binutils. Not obvious why it is failing though.
A git bisect tracks the problem down to this commit.
palantir:2177$ git bisect bad
c1baaddf8861aea666b84baeb4746caff51a579d is the first bad commit
commit c1baaddf88
On Tue, Jun 14, 2016 at 11:37 AM, Christophe Lyon
wrote:
> On 14 June 2016 at 14:07, Jérôme Forissier
> wrote:
>> Hi,
>>
>> I've stumbled across an assembler error message that I don't understand.
>>
>> bl1/aarch64/bl1_exceptions.S: Assembler messages:
>> bl1/aarch64/bl1_exceptions.S:53: Error
On 14 June 2016 at 14:07, Jérôme Forissier wrote:
> Hi,
>
> I've stumbled across an assembler error message that I don't understand.
>
> bl1/aarch64/bl1_exceptions.S: Assembler messages:
> bl1/aarch64/bl1_exceptions.S:53: Error: non-constant expression in
> ".if" statement
>
> It occurs when bui
Hi,
I've stumbled across an assembler error message that I don't understand.
bl1/aarch64/bl1_exceptions.S: Assembler messages:
bl1/aarch64/bl1_exceptions.S:53: Error: non-constant expression in
".if" statement
It occurs when building ARM Trusted Firmware with aarch64-linux-gnu-gcc
that ships w
