New issue
Advanced search Search tips

Issue 757914 link

Starred by 1 user
Status: Verified
Owner:
cmt...@chromium.org
Closed: Aug 2017
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

app-benchmarks/punybench: revert to build with GCC.

Project Member Reported by cmt...@chromium.org, Aug 22 2017 
The app-benchmarks/punybench package needs to be reverted to build with GCC.  The package uses the -pg flag which causes clang, by default, to generate the symbol "mcount", which the linker cannot resolve.  Passing "-meabi gnu" fixes that issue by causing clang to generate "__gnu_mcount_nc" instead, but LLVM's current implementation of that is incorrect and can corrupt the stack pointer. (see https://bugs.llvm.org/show_bug.cgi?id=33845)
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 26 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/204643a86738a7a532ccfd6134225fbe8e4bb07d

commit 204643a86738a7a532ccfd6134225fbe8e4bb07d
Author: Caroline Tice <cmtice@google.com>
Date: Sat Aug 26 21:55:53 2017

Revert punybench to building with GCC.

There is an upstream bug with the LLVM implementation of
__gnu_mcount_nc (generated with the '-meabi gnu' option), that
can corrupt the stack pointer.  Force this package to build
with GCC until the upstream bug is fixed.
(https://bugs.llvm.org/show_bug.cgi?id=33845)

BUG= chromium:757914 
TEST=emerge-daisy app-benchmarks/punybench, built with GCC.

Change-Id: If6b0933caa019779d53cc9455787101dd65108a6
Reviewed-on: https://chromium-review.googlesource.com/627082
Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Caroline Tice <cmtice@chromium.org>
Reviewed-by: Luis Lozano <llozano@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/204643a86738a7a532ccfd6134225fbe8e4bb07d/app-benchmarks/punybench/punybench-9999.ebuild

Comment 2 by cmt...@chromium.org, Aug 28 2017

Status: Fixed (was: Assigned)

Comment 3 by cmt...@chromium.org, Sep 25 2017

Status: Verified (was: Fixed)
►

Sign in to add a comment