public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tg at mirbsd dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/49856] ICE when compiling mktime.c (gnulib, embedded in libvirt) Date: Tue, 26 Jul 2011 20:05:00 -0000 [thread overview] Message-ID: <bug-49856-4-4dYgsasWmQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49856-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49856 --- Comment #1 from Thorsten Glaser <tg at mirbsd dot org> 2011-07-26 20:04:49 UTC --- Also applies to 4.6.1-4: root@ara5:~ # /usr/lib/m68k-linux-gnu/gcc/m68k-linux-gnu/4.6.1/cc1 -fpreprocessed y.i -m68020 -O2 -o y.s __strcspn_c1 __strcspn_c2 __strcspn_c3 __strspn_c1 __strspn_c2 __strspn_c3 __strpbrk_c2 __strpbrk_c3 __strtok_r_1c __strsep_1c __strsep_2c __strsep_3c leapyear isdst_differ ydhms_diff time_t_avg time_t_add_ok time_t_int_add_ok guess_time_tm ranged_convert mktime_internal rpl_mktime Analyzing compilation unit Performing interprocedural optimizations <*free_lang_data> <visibility> <early_local_cleanups> <whole-program> <ipa-profile> <cp> <inline> <pure-const> <static-var>Assembling functions: ranged_convert y.i: In function ‘ranged_convert’: y.i:632:1: internal compiler error: in m68k_sched_issue_rate, at config/m68k/m68k.c:6055 Please submit a full bug report,
next prev parent reply other threads:[~2011-07-26 20:05 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-26 19:56 [Bug target/49856] New: " tg at mirbsd dot org 2011-07-26 20:05 ` tg at mirbsd dot org [this message] 2011-07-26 20:25 ` [Bug target/49856] " mikpe at it dot uu.se 2011-07-26 20:58 ` schwab@linux-m68k.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-49856-4-4dYgsasWmQ@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).