public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/32494] gcc-4.3.x _32-bit_ becoming irrelevant to kernel
Date: Fri, 29 Jun 2007 21:45:00 -0000	[thread overview]
Message-ID: <20070629214508.7212.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32494-11706@http.gcc.gnu.org/bugzilla/>



------- Comment #17 from pinskia at gcc dot gnu dot org  2007-06-29 21:45 -------
1) The compiler needs a support library to implement all required features in
the standard.
2) That library is libgcc.
3) Linux kernel has its own support library for these functions
4) The linux kernel support library for C is not complete.

So where is the GCC bug if the linux support library not complete?


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


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


  parent reply	other threads:[~2007-06-29 21:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 12:12 [Bug c/32494] New: " malitzke at metronets dot com
2007-06-25 12:16 ` [Bug c/32494] " pinskia at gcc dot gnu dot org
2007-06-25 12:33 ` pinskia at gcc dot gnu dot org
2007-06-25 12:35 ` malitzke at metronets dot com
2007-06-25 12:37 ` pinskia at gcc dot gnu dot org
2007-06-25 12:50 ` malitzke at metronets dot com
2007-06-25 12:53 ` rguenth at gcc dot gnu dot org
2007-06-25 12:54 ` pinskia at gcc dot gnu dot org
2007-06-25 13:03 ` malitzke at metronets dot com
2007-06-25 13:07 ` pinskia at gcc dot gnu dot org
2007-06-25 17:01 ` malitzke at metronets dot com
2007-06-25 17:12 ` pinskia at gcc dot gnu dot org
2007-06-28  3:53 ` malitzke at metronets dot com
2007-06-28 19:06 ` pinskia at gcc dot gnu dot org
2007-06-29 21:14 ` malitzke at metronets dot com
2007-06-29 21:20 ` pinskia at gcc dot gnu dot org
2007-06-29 21:42 ` malitzke at metronets dot com
2007-06-29 21:45 ` pinskia at gcc dot gnu dot org [this message]
2007-06-29 22:19 ` malitzke at metronets dot com
2007-06-29 22:34 ` schwab at suse dot de
2007-06-29 23:53 ` malitzke at metronets dot com
2007-06-29 23:55 ` pinskia at gcc dot gnu dot org
2007-06-29 23:57 ` pinskia at gcc dot gnu dot org
2007-06-30  0:18 ` malitzke at metronets dot com
2007-06-30  0:22 ` malitzke at metronets dot com
2007-06-30  0:30 ` pinskia at gcc dot gnu dot org
2007-06-30  0:31 ` 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=20070629214508.7212.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).