public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bbergua at arcos dot inf dot uc3m dot es" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/26023] Compiler crash when using -Wall and "%#ld" inside a printf.
Date: Sun, 29 Jan 2006 23:56:00 -0000	[thread overview]
Message-ID: <20060129235601.25034.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26023-12094@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from bbergua at arcos dot inf dot uc3m dot es  2006-01-29 23:56 -------
(In reply to comment #0)
> On Debian sarge the compiler crash when using -Wall and "%#ld" inside a printf.
> The file foo.c is:
> void foo() {
>         long bar;
>         printf("%#ld", bar);
> }
> 
> Compile with:
> $gcc -v -save-temps -Wall -c foo.c
> Leyendo especificaciones de /usr/lib/gcc-lib/i486-linux/3.3.5/specs
> Configurado con: ../src/configure -v
> --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
> --mandir=/usr/share/man --infodir=/usr/share/info
> --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared
> --enable-__cxa_atexit --with-system-zlib --enable-nls
> --without-included-gettext --enable-clocale=gnu --enable-debug
> --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux
> Modelo de hilos: posix
> gcc versi&#65533; 3.3.5 (Debian 1:3.3.5-13)
>  /usr/lib/gcc-lib/i486-linux/3.3.5/cc1 -E -quiet -v -D__GNUC__=3
> -D__GNUC_MINOR__=3 -D__GNUC_PATCHLEVEL__=5 foo.c -Wall foo.i
> ignorando el directorio inexistente "/usr/i486-linux/include"
> la bsqueda de #include "..." inicia aqu&#65533;
> la bsqueda de #include <...> inicia aqu&#65533;
>  /usr/local/include
>  /usr/lib/gcc-lib/i486-linux/3.3.5/include
>  /usr/include
> Fin de la lista de bsqueda.
>  /usr/lib/gcc-lib/i486-linux/3.3.5/cc1 -fpreprocessed foo.i -quiet -dumpbase
> foo.c -auxbase foo -Wall -version -o foo.s
> GNU C version 3.3.5 (Debian 1:3.3.5-13) (i486-linux)
>         compiled by GNU C version 3.3.5 (Debian 1:3.3.5-13).
> GGC heur&#65533;ticas: --param ggc-min-expand=38 --param ggc-min-heapsize=15892
> foo.c: En la funci&#65533; `foo':
> foo.c:3: aviso: implicit declaration of function `printf'
> foo.c:3: aviso: se us&#65533;
> Error interno del compilador: Error al reportar rutinas reentradas.
> Please submit a full bug report,
> with preprocessed source if appropriate.
> For Debian GNU/Linux specific bug reporting instructions, see
> <URL:http://gcc.gnu.org/bugs.html>.
> 
> Generated foo.i is:
> # 1 "foo.c"
> # 1 "<interno>"
> # 1 "<l\355nea de orden>"
> # 1 "foo.c"
> void foo() {
>         long bar;
>         printf("%#ld", bar);
> }
> 
> Generated foo.s is:
>         .file   "foo.c"
> 

(In reply to comment #1)
> What LC_*/LANG env variables you have set?
> 

Yes, sorry, spanish:
echo $LANG
es_ES.UTF-8

I haven't got any LC_*


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26023


  parent reply	other threads:[~2006-01-29 23:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-29 23:39 [Bug c/26023] New: " bbergua at arcos dot inf dot uc3m dot es
2006-01-29 23:40 ` [Bug c/26023] " pinskia at gcc dot gnu dot org
2006-01-29 23:56 ` bbergua at arcos dot inf dot uc3m dot es [this message]
2006-01-30  0:15 ` [Bug translation/26023] " pinskia at gcc dot gnu dot 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=20060129235601.25034.qmail@sourceware.org \
    --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: 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).