public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vineetgupta22 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/60321] New: compiler error: in gcov_open, at gcov-io.c:82 Date: Sat, 22 Feb 2014 20:32:00 -0000 [thread overview] Message-ID: <bug-60321-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60321 Bug ID: 60321 Summary: compiler error: in gcov_open, at gcov-io.c:82 Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: major Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: vineetgupta22 at gmail dot com Host: i686-pc-mingw32 Target: i686-pc-mingw32 Build: i686-pc-cygwin Created attachment 32201 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32201&action=edit LawInfos - Full Project Attached Hi, I am using the Latest Compiler 4.8.2 on Cygwin Environment using Mingw32 Compiler to Create Shared Library for Cross Platforms. The details of Compiler are: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-pc-cygwin/4.8.2/lto-wrapper.exe Target: i686-pc-cygwin Configured with: /cygdrive/i/szsz/tmpp/gcc4/gcc-4.8.2-2/src/gcc-4.8.2/configure --srcdir=/cygdrive/i/szsz/tmpp/gcc4/gcc-4.8.2-2/src/gcc-4.8.2 --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --libexecdir=/usr/libexec --datadir=/usr/share --localstatedir=/var --sysconfdir=/etc --libdir=/usr/lib --datarootdir=/usr/share --docdir=/usr/share/doc/gcc --htmldir=/usr/share/doc/gcc/html -C --build=i686-pc-cygwin --host=i686-pc-cygwin --target=i686-pc-cygwin --without-libiconv-prefix --without-libintl-prefix --enable-shared --enable-shared-libgcc --enable-static --enable-version-specific-runtime-libs --enable-bootstrap --disable-__cxa_atexit --with-dwarf2 --with-arch=i686 --with-tune=generic --disable-sjlj-exceptions --enable-languages=ada,c,c++,fortran,java,lto,objc,obj-c++ --enable-graphite --enable-threads=posix --enable-libatomic --enable-libgomp --disable-libitm --enable-libquadmath --enable-libquadmath-support --enable-libssp --enable-libada --enable-libjava --enable-libgcj-sublibs --disable-java-awt --disable-symvers --with-ecj-jar=/usr/share/java/ecj.jar --with-gnu-ld --with-gnu-as --with-cloog-include=/usr/include/cloog-isl --without-libiconv-prefix --without-libintl-prefix --with-system-zlib --libexecdir=/usr/lib Thread model: posix gcc version 4.8.2 (GCC) I have attached the Full Project i.e. at Initial Stage of Development. Int the root Directory using ./bootstrap to use do my configuration options and to clean the Project Objects and other things using ./cls [written in bash]. I have also tried to compile the source in the cygwin environment it is then compiled without any error message. In attachment the ./deps and .gno files are attached which are generated by cygwin default environment. In the project I am using rdtsc for time execution and reporting. If you don't want to have any output on the screen then in LawCommonDef.h set vtrace to nothing. Vineet Gupta
next reply other threads:[~2014-02-22 20:32 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-22 20:32 vineetgupta22 at gmail dot com [this message] 2014-02-22 20:33 ` [Bug c/60321] " vineetgupta22 at gmail dot com 2014-02-22 21:00 ` [Bug gcov-profile/60321] " pinskia at gcc dot gnu.org
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=bug-60321-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).