New issue
Advanced search Search tips

Issue 747565 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 13
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Get rid of few remaining uses of GCC for x86-32 compiles

Project Member Reported by llozano@chromium.org, Jul 21 2017

Issue description

Now that there are no more boards built with x86-32, we should get rif of the remaining uses of GCC for x86-32.

See this for an example:

https://chromium-review.googlesource.com/c/579800

it also looks like chrome maybe using 32-bit compiles for the host. 
We should try to convert these to 64-bit compiles when possible. 
ie: reduce to a minimum the use of 32-bit compiler for x86-32/64bit
 
Do we want to get rid of i686-pc-linux-gnu-gcc or
x86_64-cros-linux-gnu-gcc -m32
Currently we have following packages using 32 bit gcc when building terra (an amd64 board).
i686-pc-linux-gnu-gcc:
vboot_reference

x86_64-cros-linux-gnu-gcc -m32:
elfutils

Components: Infra

Comment 4 by mmoss@chromium.org, Jan 2 2018

Components: -Infra Infra>Client>ChromeOS
[It appears that a bunch of old cros issues bulk-added the "Infra" component recently, but they should probably be "Infra>Client>ChromeOS".]
Components: -Infra>Client>ChromeOS
Components: Tools>ChromeOS-Toolchain
Owner: manojgupta@chromium.org
Status: WontFix (was: Assigned)
We use clang now for 32-bit compiles (when needed in 64 bit mode).
Any other uses of GCC are forced uses and not related to the bug.

Sign in to add a comment