Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Relocation overflow using binutils 2.27

Fixed

Description

Hi,

We face a problem when we build chromium with AGL master branch provided binutils.

Apparently, the problem has started to appear since binutils version was bumped to 2.27, which introduced the R_AARCH64_LD64_GOTPAGE_LO15 got-relative instruction relocation and the R_AARCH64_ABS32 data relocation.

We use TARGET_CFLAGS  and TARGET_CXXFLAGS, but instead of -O2 and -fpie flags -Os and -fPIE are used, which resolves the linking problem. This is not an ideal solution as long as it leads to a decreased performance. In order to reproduce the issue, comment out lines 115, 116 and 119, 120 from https://github.com/Igalia/meta-browser/blob/ozone/wayland/20170606/recipes-browser/chromium/chromium-browser-gn.inc#L115.

Would you please take a closer look to the issue and resolve it as soon as possible? I suppose some upstream patches could be backported, which would resolve the issue.

Regards,

Maksim

Environment

AGL master branch, bundled binutils 2.27 (aarch64-agl-linux-g++ and ld.gold.), chromium m60 - [https://github.com/Igalia/meta-browser|https://github.com/Igalia/meta-browser,] hw - m3ulcb

Activity

Show:

Maksim Sisov 
December 1, 2017 at 1:11 PM

Hi ,

The problem has been resolved. You can close the issue.

Stephane Desneux 
December 1, 2017 at 1:05 PM

Hello all,

Is this issue still valid ?

Ryo Kodama 
July 27, 2017 at 7:44 AM

Hi Maksim Ronan

Sorry I had you mixed up. The question intended just to Ronan.

And I wanted to ask that how does Ronan think about the way to solve this issue.

And I'd like to know the status of this issue.

 

Yes, I have been able to reproduce the issue.

Maksim Sisov 
July 25, 2017 at 7:02 AM

Hi Ryo,

I'm sorry, but whom has it been addressed to? Just to Ronan or to Igalia as well? Have you been able to reproduce the issue?

Br,

Maksim

Ryo Kodama 
July 12, 2017 at 5:23 AM

Hi ronan

 

Do you have any updates?

I have been searched the patch in Yocto master. But I can't find out it.

And I'm poor at this issue. I don't have any good idea to solve this.

How will you solve this issue?

Will you solve it yourself? or report this upstream?

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

Created June 12, 2017 at 7:03 AM
Updated December 1, 2017 at 9:59 PM
Resolved December 1, 2017 at 1:34 PM

Flag notifications