public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "castet dot matthieu at free dot fr" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/789] HP_TIMING_ACCUM broken on ia32 ? Date: Tue, 15 Mar 2005 08:35:00 -0000 [thread overview] Message-ID: <20050315083508.21460.qmail@sourceware.org> (raw) In-Reply-To: <20050314140930.789.castet.matthieu@free.fr> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1967 bytes --] ------- Additional Comments From castet dot matthieu at free dot fr 2005-03-15 08:35 ------- Created an attachment (id=434) --> (http://sources.redhat.com/bugzilla/attachment.cgi?id=434&action=view) testcase in src/nptl : $ gcc /tmp/test.c -std=gnu99 -O2 -Wall -Winline -Wstrict-prototypes -Wwrite-strings -g -mpreferred-stack-boundary=2 -I../include -I. -I/home/castetm/trace/contrib/libc_compil/build/nptl -I.. -I../libio -I/home/castetm/trace/contrib/libc_compil/build -I../sysdeps/i386/elf -I../nptl/sysdeps/unix/sysv/linux/i386/i686 -I../nptl/sysdeps/unix/sysv/linux/i386 -I../nptl/sysdeps/unix/sysv/linux -I../nptl/sysdeps/pthread -I../sysdeps/pthread -I../nptl/sysdeps/unix/sysv -I../nptl/sysdeps/unix -I../nptl/sysdeps/i386/i686 -I../nptl/sysdeps/i386 -I../sysdeps/unix/sysv/linux/i386 -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386 -I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/i386/i686/fpu -I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../nptl/sysdeps/i386/i486 -I../sysdeps/i386/fpu -I../sysdeps/i386 -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic -D_LIBC_REENTRANT -D_LIBC_REENTRANT -include ../include/libc-symbols.h -DNOT_IN_libc=1 -DIS_IN_libpthread=1 -o /tmp/test /tmp/test.c:4: attention : function declaration isn't a prototype /tmp/test.c: Dans la fonction « main »: /tmp/test.c:20: attention : implicit declaration of function `printf' /tmp/test.c:18: error: impossible register constraint in `asm' /tmp/test.c:21: embrouillé par les erreurs précédentes, abandon -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=789 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-03-15 8:35 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-14 14:09 [Bug libc/789] New: " castet dot matthieu at free dot fr 2005-03-15 0:30 ` [Bug libc/789] " gotom at debian dot or dot jp 2005-03-15 7:19 ` jakub at redhat dot com 2005-03-15 8:31 ` castet dot matthieu at free dot fr 2005-03-15 8:35 ` castet dot matthieu at free dot fr [this message] 2005-03-15 10:15 ` jakub at redhat dot com 2005-03-15 14:27 ` castet dot matthieu at free dot fr 2005-03-15 14:34 ` castet dot matthieu at free dot fr 2005-03-15 22:31 ` cvs-commit at gcc dot gnu dot org 2005-03-16 9:14 ` castet dot matthieu at free dot fr 2005-03-22 12:09 ` castet dot matthieu at free dot fr 2005-09-23 19:11 ` drepper at redhat dot com 2005-09-23 20:17 ` castet dot matthieu at free dot fr
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=20050315083508.21460.qmail@sourceware.org \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs@sources.redhat.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: 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).