gcc

Merge lp://staging/~christophe-lyon/gcc/4.8-sanitizer into lp://staging/gcc

  1. 4.8-sanitizer
  2. Merge into trunk
Proposed by Christophe Lyon
Status: Superseded
Proposed branch: lp://staging/~christophe-lyon/gcc/4.8-sanitizer
Merge into: lp://staging/gcc
To merge this branch: bzr merge lp://staging/~christophe-lyon/gcc/4.8-sanitizer
Reviewer Review Type Date Requested Status
Linaro Toolchain Builder Pending
Review via email: mp+160087@code.staging.launchpad.net

This proposal supersedes a proposal from 2013-03-26.

This proposal has been superseded by a proposal from 2013-04-23.

Description of the change

Enable libsanitizer on ARM.
Branch created to check behaviour on board instead of qemu.

First submission gave good results.

The 2nd attempt bundles -funwind-tables with -fsanitize=* for user convenience.

This merge request still serves as a test on board before sending the patch upstream.

On qemu, the following problems have been observed:
- support of /proc/self/maps does not conform to the kernel format.
  One extra space is missing from some lines, which confuses libsanitizer.
  Patch proposed to upstream qemu:
  http://lists.gnu.org/archive/html/qemu-devel/2013-02/msg03051.html

- qemu reserves some memory space by default, conflicting with libsanitizer needs.
  Workaround: invoke qemu with -R 0

- libsanitizer detects if its output is a tty, and when GCC testsuite is executed under qemu, libsanitizer concludes that it is actually running under a tty, and adds beautyfying characters which confuse dejanu.

The 3rd submission:
- modifies some regexps to cope with the tty problem described above. Should have no impact when run under qemu
- skips some tests when run on simuator (clone-test-1, rlimit-mmap-test-1.c)

To post a comment you must log in.
Revision history for this message
Linaro Toolchain Builder (cbuild) wrote : Posted in a previous version of this proposal

cbuild has taken a snapshot of this branch at r122157 and queued it for build.

The diff against the ancestor r122156 is available at:
 http://cbuild.validation.linaro.org/snapshots/gcc-4.8+bzr122157~christophe-lyon~4.8-sanitizer.diff

and will be built on the following builders:
 a9-builder a9hf-builder armv5-builder i686 x86_64 xaarch64 xaarch64_bare xcortexa15hf

You can track the build queue at:
 http://cbuild.validation.linaro.org/helpers/scheduler

cbuild-snapshot: gcc-4.8+bzr122157~christophe-lyon~4.8-sanitizer
cbuild-ancestor: lp:gcc+bzr122156
cbuild-state: check

Revision history for this message
Linaro Toolchain Builder (cbuild) wrote : Posted in a previous version of this proposal

cbuild has taken a snapshot of this branch at r122158 and queued it for build.

The diff against the ancestor r122156 is available at:
 http://cbuild.validation.linaro.org/snapshots/gcc-4.8+bzr122158~christophe-lyon~4.8-sanitizer.diff

and will be built on the following builders:
 a9-builder a9hf-builder armv5-builder i686 x86_64 xaarch64 xaarch64_bare xcortexa15hf

You can track the build queue at:
 http://cbuild.validation.linaro.org/helpers/scheduler

cbuild-snapshot: gcc-4.8+bzr122158~christophe-lyon~4.8-sanitizer
cbuild-ancestor: lp:gcc+bzr122156
cbuild-state: check

Revision history for this message
Linaro Toolchain Builder (cbuild) wrote :

cbuild has taken a snapshot of this branch at r122159 and queued it for build.

The diff against the ancestor r122156 is available at:
 http://cbuild.validation.linaro.org/snapshots/gcc-4.8+bzr122159~christophe-lyon~4.8-sanitizer.diff

and will be built on the following builders:
 a9-builder a9hf-builder armv5-builder i686 x86_64 xaarch64 xaarch64_bare xcortexa15hf

You can track the build queue at:
 http://cbuild.validation.linaro.org/helpers/scheduler

cbuild-snapshot: gcc-4.8+bzr122159~christophe-lyon~4.8-sanitizer
cbuild-ancestor: lp:gcc+bzr122156
cbuild-state: check

Subscribers

People subscribed via source and target branches

to all changes: