Re: GCC's instrumentation and the target environment
On 11/4/19 2:06 PM, david.tay...@dell.com wrote: From: Martin Liška Sent: Monday, November 4, 2019 4:20 AM To: taylor, david; gcc@gcc.gnu.org Subject: Re: GCC's instrumentation and the target environment On 11/1/19 7:13 PM, David Taylor wrote: Hello. Hello. What I'd like is a stable API between the routines that 'collect' the data and the routines that do the i/o. With the i/o routines being non-static and in a separate file from the others that is not #include'd. I want them to be replaceable by the application. Depending upon circumstances I can imagine the routines doing network i/o, disk i/o, or using a serial port. What's difference in between i/o and disk i/o? What about using a NFS file system into which you can save the data (via -fprofile-dir=/mnt/mynfs/...)? I/O encompasses more than just reading and writing a file in a file system. Depending on the embedded target you might not have the ability to NFS mount. You might not even have a file system accessible to instrumentation. By network I/O I'm thinking sockets. There's some code possibly run at 'boot' time or possibly run during the first __gcov_open that establishes a network connection with a process running on another system. There's some protocol, agreed to by the application and remote process, for communicating the data collected and which file it belongs to. By serial I/O, I'm thinking of a serial port. Hello. I see your needs. I would recommend to come up with patches that will enable such a communication channel. I can review the patches or help you with obstacles. Martin Hopefully that is clearer. I can imagine dump into stderr for example. That can be quite easily doable. I don't think that the current implementation would make that easy. For us there are potentially over a thousand files being instrumented. You need to communicate which file the data belongs to. Whether it is via stderr, a serial port, or a network connection, the file name needs to be in the stream and there needs to be a way of determining when one file ends and the next one begins. For us, stderr and stdout, when defined, are used for communicating status and extraordinary events. And not well suited for transferring instrumentation data. Martin David
We are looking this website for post-https://gcc.gnu.org/
HI Sir We are looking this website for post-https://gcc.gnu.org/ I am working from some years and our company is well reputed. We have lots of clients for whom we are working. our client need good sites with the following features Alex Rank - Less than 100 OR DA 50+ Sites so please send me sites with post price. Note - Do not send me sites, you can not post our article with do-follow link.. We will send you payment within 48 hour after publish post and we will send to our clients as the approved we will send u payment with 48 hour Waiting
Re: GCC wwwdocs move to git done
Am 09.10.19 um 02:27 schrieb Joseph Myers: I've done the move of GCC wwwdocs to git (using the previously posted and discussed scripts), including setting up the post-receive hook to do the same things previously covered by the old CVS hooks, and minimal updates to the web pages dealing with the CVS setup for wwwdocs. Hi, May it be the case that some parts are missing? In particular, I cannot find the source of https://gcc.gnu.org/install/configure.html Johann
Re: GCC wwwdocs move to git done
Am 06.11.19 um 15:03 schrieb Georg-Johann Lay: Am 09.10.19 um 02:27 schrieb Joseph Myers: I've done the move of GCC wwwdocs to git (using the previously posted and discussed scripts), including setting up the post-receive hook to do the same things previously covered by the old CVS hooks, and minimal updates to the web pages dealing with the CVS setup for wwwdocs. Hi, May it be the case that some parts are missing? In particular, I cannot find the source of https://gcc.gnu.org/install/configure.html Johann Ok, found it in install/README. knew it had something special about it... Johann
URGENT REPLY NEEDED
WHY HAVE I NOT HEARD FROM YOU?
[Darwin, testsuite, committed] Fix framework-1.c on later Darwin.
The test works by checking that a known framework path is accessible
when the '-F' option is given. We need to find a framework path that
exists across a range of Darwin versions, and parseable by GCC. This
adjusts the test to use a header path that exists and is parsable from
Darwin9 through Darwin19.
tested with Darwin9 through Darwin19 SDKs on x86-64-darwin16,
applied to mainline,
thanks
Iain
gcc/testsuite/ChangeLog:
2019-11-06 Iain Sandoe
* gcc.dg/framework-1.c: Adjust test header path.
diff --git a/gcc/testsuite/gcc.dg/framework-1.c
b/gcc/testsuite/gcc.dg/framework-1.c
index 7e68683..de4adc3 100644
--- a/gcc/testsuite/gcc.dg/framework-1.c
+++ b/gcc/testsuite/gcc.dg/framework-1.c
@@ -1,4 +1,4 @@
/* { dg-do compile { target *-*-darwin* } } */
/* { dg-options "-F." } */
-#include
+#include
Build Status - Successful Build & Install
srcdir/config.guess: x86_64-pc-linux-gnu gcc -v output: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../srcdir/configure --disable-multilib Thread model: posix gcc version 9.2.0 (GCC) It was a Linux build. Distribution name&version: Ubuntu 18.04.3 LTS Linux kernel version: 5.0.0-32-generic glibc version: 2.27-3ubuntu (both amd64 and i386)
RE:elektronicka faktura 1782413781
--- Vazeni, Vase fakturuv priloze, S pozdravem. faktura_0005844.docx Description: Binary data
make all failed with error for GCC 9.2
Hi, I was trying to build GCC and "make all" is failing. Please find the config.log below and kindly help me to rectify this issue. Thanks and Regards, Aj This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by configure, which was generated by GNU Autoconf 2.69. Invocation command line was $ ../gcc-9.2.0/configure --target=powerpc-eabi --prefix=/usr/local/powerpc-eabi --with-newlib --with-gnu-as --with-gnu-ld --disable-shared --disable-libssp ## - ## ## Platform. ## ## - ## hostname = Ubuntu-18-04 uname -m = x86_64 uname -r = 4.15.0-66-generic uname -s = Linux uname -v = #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /usr/local/powerpc-eabi/bin PATH: /home/ajupazhamayil/.local/bin PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/sbin PATH: /usr/bin PATH: /sbin PATH: /bin PATH: /usr/games PATH: /usr/local/games PATH: /snap/bin PATH: /snap/bin PATH: /var/lib/snapd/snap/bin PATH: /mnt/films/riscvInstall/bin PATH: /mnt/films/riscvInstall/riscv64-unknown-elf/bin ## --- ## ## Core tests. ## ## --- ## configure:2352: checking build system type configure:2366: result: x86_64-pc-linux-gnu configure:2413: checking host system type configure:2426: result: x86_64-pc-linux-gnu configure:2446: checking target system type configure:2459: result: powerpc-unknown-eabi configure:2513: checking for a BSD-compatible install configure:2581: result: /usr/bin/install -c configure:2592: checking whether ln works configure:2614: result: yes configure:2618: checking whether ln -s works configure:2622: result: yes configure:2629: checking for a sed that does not truncate output configure:2693: result: /bin/sed configure:2702: checking for gawk configure:2718: found /usr/bin/gawk configure:2729: result: gawk configure:3223: checking for libatomic support configure:3229: result: no configure:3261: checking for libitm support configure:3267: result: no configure:3280: checking for libsanitizer support configure:3286: result: no configure:3299: checking for libvtv support configure:3305: result: no configure:3319: checking for libhsail-rt support configure:3325: result: no configure:3410: checking for libphobos support configure:3416: result: no configure:4080: checking for gcc configure:4096: found /usr/bin/gcc configure:4107: result: gcc configure:4336: checking for C compiler version configure:4345: gcc --version >&5 gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:4356: $? = 0 configure:4345: gcc -v >&5 Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --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 --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) configure:4356: $? = 0 configure:4345: gcc -V >&5 gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files compilation terminated. configure:4356: $? = 1 configure:4345: gcc -qversion >&5 gcc: error: unrecognized command line option '-qversion'; did you mean '--version'? gcc: fatal error: no input files compilation terminated. configure:4356: $? = 1 configure:4376: checking whether the C compiler works configure:4398: gccconftest.c >&5 configure:4402: $? = 0 configure:4450: result: yes configure:4453: checking for C compiler default output file name configure:4455: result: a.out configure:4461: checking for su
