From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: YunQiang Su <wzssyqa@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] gprofng: 30700 tmpdir/gp-collect-app_F test fails
Date: Thu, 17 Aug 2023 22:01:56 -0700 [thread overview]
Message-ID: <bbc6cfb0-8505-6a98-cd11-fe1c06c269b0@oracle.com> (raw)
In-Reply-To: <CAKcpw6XiomzAJC_qOqejSwdi_0hDt3FJcsJX1G+Z_c=CNt7KaQ@mail.gmail.com>
On 8/17/23 19:11, YunQiang Su wrote:
> Vladimir Mezentsev <vladimir.mezentsev@oracle.com> 于2023年8月18日周五 02:44写道：
>> I cannot reproduce the problem on this Debian:
>> % uname -a
>> Linux gcc14 6.1.0-11-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-4
>> (2023-08-08) x86_64 GNU/Linux
>>
> $ uname -a
> Linux vm-1 6.0.0-0.deb11.6-amd64 #1 SMP PREEMPT_DYNAMIC Debian
> 6.0.12-1~bpo11+1 (2022-12-19) x86_64 GNU/Linux
>
> $ gcc -v
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
> OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
> OFFLOAD_TARGET_DEFAULT=1
> Target: x86_64-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Debian
> 12.2.0-14' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs
> --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2
> --prefix=/usr --with-gcc-major-version-only --program-suffix=-12
> --program-prefix=x86_64-linux-gnu- --enable-shared
> --enable-linker-build-id --libexecdir=/usr/lib
> --without-included-gettext --enable-threads=posix --libdir=/usr/lib
> --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
> --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
> --enable-gnu-unique-object --disable-vtable-verify --enable-plugin
> --enable-default-pie --with-system-zlib
> --enable-libphobos-checking=release --with-target-system-zlib=auto
> --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet
> --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32
> --enable-multilib --with-tune=generic
> --enable-offload-targets=nvptx-none=/build/gcc-12-bTRWOB/gcc-12-12.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-bTRWOB/gcc-12-12.2.0/debian/tmp-gcn/usr
> --enable-offload-defaulted --without-cuda-driver
> --enable-checking=release --build=x86_64-linux-gnu
> --host=x86_64-linux-gnu --target=x86_64-linux-gnu
> Thread model: posix
> Supported LTO compression algorithms: zlib zstd
> gcc version 12.2.0 (Debian 12.2.0-14)
>
>> % make check
>> ...
>> Test run by vmezents on Thu Aug 17 18:32:49 2023
>> Native configuration is x86_64-pc-linux-gnu
>>
>> === gprofng tests ===
>>
>> Schedule of variations:
>> unix
>>
>> Running target unix
>> Using /usr/share/dejagnu/baseboards/unix.exp as board description file
>> for target.
>> Using /usr/share/dejagnu/config/unix.exp as generic interface file for
>> target.
>> Using
>> /home/vmezents/GPROF/binutils-gdb.git/gprofng/testsuite/config/default.exp
>> as tool-and-target-specific interface file.
>> Running
>> /home/vmezents/GPROF/binutils-gdb.git/gprofng/testsuite/gprofng.display/display.exp
>> ...
>> Running
>> /home/vmezents/GPROF/binutils-gdb.git/gprofng/testsuite/gprofng.display/gp-archive.exp
>> ...
>> Running
>> /home/vmezents/GPROF/binutils-gdb.git/gprofng/testsuite/gprofng.display/gp-collect-app_F.exp
>> ...
>> Running
>> /home/vmezents/GPROF/binutils-gdb.git/gprofng/testsuite/gprofng.display/setpath_map.exp
>> ...
>>
>> === gprofng Summary ===
>>
>> # of expected passes 6
>> make[2]: Leaving directory '/home/vmezents/GPROF/dist_binutils-gdb/gprofng'
>> make[1]: Leaving directory '/home/vmezents/GPROF/dist_binutils-gdb/gprofng'
>>
>>
>>
>> How did you configure your build ?
> mkdir x86_64-linux-gnu
> cd x86_64-linux-gnu
> ../configure --target=x86_64-linux-gnu --disable-gdb --disable-sim
Is it legal to create a build directory inside a source tree?
Anyway, I found a bug in our script.
I haven't found yet why the test passes if I create the build directory
outside of the source tree.
Thank you,
-Vladimir
>
>> Could you send me gprofng/gprofng.log from your build directory.
>>
> See the attachment.
>
>> Thank you,
>> -Vladimir
>>
>>
next prev parent reply other threads:[~2023-08-18 5:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 20:33 vladimir.mezentsev
2023-08-17 4:22 ` YunQiang Su
2023-08-17 18:44 ` Vladimir Mezentsev
2023-08-18 2:11 ` YunQiang Su
2023-08-18 5:01 ` Vladimir Mezentsev [this message]
2023-08-18 5:09 ` YunQiang Su
2023-08-18 5:10 ` Sam James
2023-08-18 6:38 ` Matthias Klose
2023-08-18 6:45 ` Sam James
[not found] ` <f4c4c9956ccb5bc55fe95f51ee858e3558aa6acbe8d0d0ca0e8716bafbc1fbab@mu.id>
2023-08-18 6:49 ` Sam James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bbc6cfb0-8505-6a98-cd11-fe1c06c269b0@oracle.com \
--to=vladimir.mezentsev@oracle.com \
--cc=binutils@sourceware.org \
--cc=wzssyqa@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).