Bug#862176: gcc-snapshot: needs packages from experimental, with -fsanitize=address

2017-05-09 Thread Vincent Lefevre 
On 2017-05-10 03:26:14 +0200, Vincent Lefevre wrote:
> Forget that. This breaks the use of LD_RUN_PATH. :( Or the contents
> of LD_RUN_PATH should be added as rpath arguments by the wrapper.

In case this can be useful:

#!/bin/sh
LD_LIBRARY_PATH=/usr/lib/gcc-snapshot/lib:$LD_LIBRARY_PATH
PATH=/usr/lib/gcc-snapshot/bin:$PATH
rpath=""
OLD_IFS="$IFS"
IFS=:
for i in $LD_RUN_PATH
do
  rpath="$rpath -Wl,-rpath -Wl,$i"
done
IFS="$OLD_IFS"
exec gcc -Wl,-rpath -Wl,/usr/lib/gcc-snapshot/lib \
 -Wl,-rpath -Wl,/usr/lib/gcc-snapshot/lib32 \
 -Wl,-rpath -Wl,/usr/lib/gcc-snapshot/libx32 $rpath "$@"

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#862176: gcc-snapshot: needs packages from experimental, with -fsanitize=address

2017-05-09 Thread Vincent Lefevre 
On 2017-05-10 01:31:02 +0200, Vincent Lefevre wrote:
> > closing this issue, there is no "propoer" solution.
> 
> I'm just thinking... Couldn't the use of a run path for
> /usr/lib/gcc-snapshot/lib be a proper solution? i.e. give
> a better wrapper as an example? For instance, on amd64,
> the wrapper could be:
> 
> --- snip --
> #!/bin/sh
> LD_LIBRARY_PATH=/usr/lib/gcc-snapshot/lib:$LD_LIBRARY_PATH
> PATH=/usr/lib/gcc-snapshot/bin:$PATH
> exec gcc -Wl,-rpath -Wl,/usr/lib/gcc-snapshot/lib \
>  -Wl,-rpath -Wl,/usr/lib/gcc-snapshot/lib32 \
>  -Wl,-rpath -Wl,/usr/lib/gcc-snapshot/libx32 "$@"
> --- snip --

Forget that. This breaks the use of LD_RUN_PATH. :( Or the contents
of LD_RUN_PATH should be added as rpath arguments by the wrapper.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#862176: gcc-snapshot: needs packages from experimental, with -fsanitize=address

2017-05-09 Thread Vincent Lefevre 
Control: reopen -1
Control: severity -1 minor
Control: retitle -1 gcc-snapshot: README.Debian is inaccurate concerning 
LD_LIBRARY_PATH

On 2017-05-10 00:00:10 +0200, Matthias Klose wrote:
> set LD_LIBRARY_PATH for running your binaries.

OK, I now understand (I didn't see that gcc-snapshot provided
/usr/lib/gcc-snapshot/lib/libasan.so.4), but this was not clear.
The /usr/share/doc/gcc-snapshot/README.Debian file first says:


To use this snapshot, you should set the following environment variables:

LD_LIBRARY_PATH=/usr/lib/gcc-snapshot/lib:$LD_LIBRARY_PATH
PATH=/usr/lib/gcc-snapshot/bin:$PATH


That way, things will work. But just after, it suggests an alternate
solution:


You might also like to use a shell script to wrap up this 
funcationality, e.g. 
 
place in /usr/local/bin/gcc-snapshot and chmod +x it 
 
--- snip --
#! /bin/sh
LD_LIBRARY_PATH=/usr/lib/gcc-snapshot/lib:$LD_LIBRARY_PATH
PATH=/usr/lib/gcc-snapshot/bin:$PATH
gcc "$@"
--- snip --

Make the same for g++, g77, gij, gcj, cpp, ...


This is the solution I'm currently using, but as you say, this may
not be sufficient. There should be some warning saying that under
some conditions, such as the use of the address sanitizer, the
LD_LIBRARY_PATH will also be needed for the generated binaries.
Or...

> closing this issue, there is no "propoer" solution.

I'm just thinking... Couldn't the use of a run path for
/usr/lib/gcc-snapshot/lib be a proper solution? i.e. give
a better wrapper as an example? For instance, on amd64,
the wrapper could be:

--- snip --
#!/bin/sh
LD_LIBRARY_PATH=/usr/lib/gcc-snapshot/lib:$LD_LIBRARY_PATH
PATH=/usr/lib/gcc-snapshot/bin:$PATH
exec gcc -Wl,-rpath -Wl,/usr/lib/gcc-snapshot/lib \
 -Wl,-rpath -Wl,/usr/lib/gcc-snapshot/lib32 \
 -Wl,-rpath -Wl,/usr/lib/gcc-snapshot/libx32 "$@"
--- snip --

This seems to work (I've tested on amd64 with and without -m32).
Wouldn't this be a better solution?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: Bug#862176: gcc-snapshot: needs packages from experimental, with -fsanitize=address

2017-05-09 Thread Debian Bug Tracking System 
Processing control commands:

> reopen -1
Bug #862176 {Done: Matthias Klose } [gcc-snapshot] 
gcc-snapshot: needs packages from experimental, with -fsanitize=address
Bug reopened
Ignoring request to alter fixed versions of bug #862176 to the same values 
previously set
> severity -1 minor
Bug #862176 [gcc-snapshot] gcc-snapshot: needs packages from experimental, with 
-fsanitize=address
Severity set to 'minor' from 'important'
> retitle -1 gcc-snapshot: README.Debian is inaccurate concerning 
> LD_LIBRARY_PATH
Bug #862176 [gcc-snapshot] gcc-snapshot: needs packages from experimental, with 
-fsanitize=address
Changed Bug title to 'gcc-snapshot: README.Debian is inaccurate concerning 
LD_LIBRARY_PATH' from 'gcc-snapshot: needs packages from experimental, with 
-fsanitize=address'.

-- 
862176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#862176: marked as done (gcc-snapshot: needs packages from experimental, with -fsanitize=address)

2017-05-09 Thread Debian Bug Tracking System 
Your message dated Wed, 10 May 2017 00:00:10 +0200
with message-id <51d44b04-d261-b070-e68a-5dbf41927...@debian.org>
and subject line Re: Bug#862176: gcc-snapshot: needs packages from 
experimental, with -fsanitize=address
has caused the Debian Bug report #862176,
regarding gcc-snapshot: needs packages from experimental, with 
-fsanitize=address
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
862176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-snapshot
Version: 20170505-1
Severity: important

If I compile a program with

  gcc-snapshot -fsanitize=address

I get when running it:

./a.out: error while loading shared libraries: libasan.so.4: cannot open shared 
object file: No such file or directory

libasan.so.4 is part of libasan4, which exists only in experimental,
while gcc-snapshot 20170505-1 is in unstable.

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/12 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gcc-snapshot depends on:
ii  binutils2.28-4
ii  libc6   2.24-10
ii  libc6-dev   2.24-10
ii  libc6-dev-i386  2.24-10
ii  libc6-dev-x32   2.24-10
ii  libc6-i386  2.24-10
ii  libc6-x32   2.24-10
ii  libgc1c21:7.4.2-8
ii  libgmp102:6.1.2+dfsg-1
ii  libisl150.18-1
ii  libmpc3 1.0.3-1+b2
ii  libmpfr43.1.5-1
ii  python  2.7.13-2
ii  zlib1g  1:1.2.8.dfsg-5

gcc-snapshot recommends no packages.

Versions of packages gcc-snapshot suggests:
ii  binutils [binutils-gold]  2.28-4

-- no debconf information
--- End Message ---
--- Begin Message ---
On 09.05.2017 15:48, Vincent Lefevre wrote:
> Package: gcc-snapshot
> Version: 20170505-1
> Severity: important
> 
> If I compile a program with
> 
>   gcc-snapshot -fsanitize=address
> 
> I get when running it:
> 
> ./a.out: error while loading shared libraries: libasan.so.4: cannot open 
> shared object file: No such file or directory
> 
> libasan.so.4 is part of libasan4, which exists only in experimental,
> while gcc-snapshot 20170505-1 is in unstable.

set LD_LIBRARY_PATH for running your binaries.  The libasan4 package isn't based
on the trunk, but on the gcc-7-branch, so it might be different.

closing this issue, there is no "propoer" solution.--- End Message ---

Results for 8.0.0 20170505 (experimental) [trunk revision 247636] (Debian 20170505-1) testsuite on mips-unknown-linux-gnu

2017-05-09 Thread Matthias Klose 
LAST_UPDATED: Fri May  5 15:03:06 UTC 2017 (revision 247636)

=== acats tests ===

=== acats Summary ===
# of expected passes2320
# of unexpected failures0
Native configuration is mips-unknown-linux-gnu

=== g++ tests ===


Running target unix
FAIL: c-c++-common/Wsizeof-pointer-memaccess2.c  -std=gnu++11 (test for excess 
errors)
FAIL: c-c++-common/Wsizeof-pointer-memaccess2.c  -std=gnu++11 (test for excess 
errors)
FAIL: c-c++-common/Wsizeof-pointer-memaccess2.c  -std=gnu++14 (test for excess 
errors)
FAIL: c-c++-common/Wsizeof-pointer-memaccess2.c  -std=gnu++14 (test for excess 
errors)
FAIL: c-c++-common/Wsizeof-pointer-memaccess2.c  -std=gnu++98 (test for excess 
errors)
FAIL: c-c++-common/Wsizeof-pointer-memaccess2.c  -std=gnu++98 (test for excess 
errors)
FAIL: g++.dg/guality/pr55665.C   -O2  line 23 p == 40
FAIL: g++.dg/guality/pr55665.C   -O2  line 23 p == 40

=== g++ Summary ===

# of expected passes202678
# of unexpected failures8
# of expected failures  758
# of unsupported tests  8922
/build/gcc-snapshot-lKZhBm/gcc-snapshot-20170505/build/gcc/xg++  version 8.0.0 
20170505 (experimental) [trunk revision 247636] (Debian 20170505-1) 

=== gcc tests ===


Running target unix
FAIL: c-c++-common/Wsizeof-pointer-memaccess2.c  -Wc++-compat  (test for excess 
errors)
FAIL: c-c++-common/Wsizeof-pointer-memaccess2.c  -Wc++-compat  (test for excess 
errors)
FAIL: gcc.dg/pr78138.c  (test for warnings, line 23)
FAIL: gcc.dg/pr78138.c  (test for warnings, line 23)
FAIL: gcc.dg/pr78138.c (test for excess errors)
FAIL: gcc.dg/pr78138.c (test for excess errors)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 25)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 25)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 30)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 30)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 35)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 35)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 40)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 40)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 45)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 45)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 52)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 52)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 59)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 59)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 66)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 66)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 73)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 73)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 80)
FAIL: gcc.dg/pr79214.c  (test for warnings, line 80)
FAIL: gcc.dg/pr79214.c (test for excess errors)
FAIL: gcc.dg/pr79214.c (test for excess errors)
FAIL: gcc.dg/pr79222.c  (test for warnings, line 12)
FAIL: gcc.dg/pr79222.c  (test for warnings, line 12)
FAIL: gcc.dg/pr79222.c (test for excess errors)
FAIL: gcc.dg/pr79222.c (test for excess errors)
FAIL: gcc.dg/pr79223.c  (test for warnings, line 26)
FAIL: gcc.dg/pr79223.c  (test for warnings, line 26)
FAIL: gcc.dg/pr79223.c  (test for warnings, line 31)
FAIL: gcc.dg/pr79223.c  (test for warnings, line 31)
FAIL: gcc.dg/pr79223.c  (test for warnings, line 36)
FAIL: gcc.dg/pr79223.c  (test for warnings, line 36)
FAIL: gcc.dg/pr79223.c (test for excess errors)
FAIL: gcc.dg/pr79223.c (test for excess errors)
FAIL: gcc.dg/uninit-19.c  (test for warnings, line 23)
FAIL: gcc.dg/uninit-19.c  (test for warnings, line 23)
FAIL: gcc.dg/uninit-19.c (test for excess errors)
FAIL: gcc.dg/uninit-19.c (test for excess errors)
FAIL: gcc.dg/graphite/scop-19.c scan-tree-dump-times graphite "number of SCoPs: 
0" 1
FAIL: gcc.dg/graphite/scop-19.c scan-tree-dump-times graphite "number of SCoPs: 
0" 1
XPASS: gcc.dg/guality/example.c   -O0  execution test
XPASS: gcc.dg/guality/example.c   -O0  execution test
XPASS: gcc.dg/guality/guality.c   -O0  execution test
XPASS: gcc.dg/guality/guality.c   -O0  execution test
XPASS: gcc.dg/guality/guality.c   -O1  execution test
XPASS: gcc.dg/guality/guality.c   -O1  execution test
XPASS: gcc.dg/guality/guality.c   -O2  execution test
XPASS: gcc.dg/guality/guality.c   -O2  execution test
XPASS: gcc.dg/guality/guality.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
XPASS: gcc.dg/guality/guality.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
XPASS: gcc.dg/guality/guality.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  execution test
XPASS: gcc.dg/guality/guality.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  execution test
XPASS: gcc.dg/guality/guality.c   -O3 -g  execution test
XPASS: gcc.dg/guality/guality.c   -O3 -g  execution test
XPASS: gcc.dg/guality/guality.c   -Os  execution test
XPASS: gcc.dg/guality/guality.c   -Os  execution test
XPASS: gcc.dg/guality/inline-params.c   -O2  execution

Bug#862176: gcc-snapshot: needs packages from experimental, with -fsanitize=address

2017-05-09 Thread Vincent Lefevre 
Package: gcc-snapshot
Version: 20170505-1
Severity: important

If I compile a program with

  gcc-snapshot -fsanitize=address

I get when running it:

./a.out: error while loading shared libraries: libasan.so.4: cannot open shared 
object file: No such file or directory

libasan.so.4 is part of libasan4, which exists only in experimental,
while gcc-snapshot 20170505-1 is in unstable.

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/12 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gcc-snapshot depends on:
ii  binutils2.28-4
ii  libc6   2.24-10
ii  libc6-dev   2.24-10
ii  libc6-dev-i386  2.24-10
ii  libc6-dev-x32   2.24-10
ii  libc6-i386  2.24-10
ii  libc6-x32   2.24-10
ii  libgc1c21:7.4.2-8
ii  libgmp102:6.1.2+dfsg-1
ii  libisl150.18-1
ii  libmpc3 1.0.3-1+b2
ii  libmpfr43.1.5-1
ii  python  2.7.13-2
ii  zlib1g  1:1.2.8.dfsg-5

gcc-snapshot recommends no packages.

Versions of packages gcc-snapshot suggests:
ii  binutils [binutils-gold]  2.28-4

-- no debconf information