public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: i-sys@gmx.net To: gcc-gnats@gcc.gnu.org Subject: c/10855: extern __inline__ does not compile Date: Mon, 19 May 2003 10:06:00 -0000 [thread overview] Message-ID: <20030519095848.27211.qmail@sources.redhat.com> (raw) >Number: 10855 >Category: c >Synopsis: extern __inline__ does not compile >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon May 19 10:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: i-sys@gmx.net >Release: gcc-3.3 >Organization: >Environment: Debian GNU/Linux Sid >Description: Hello, It appears that gcc-3.3 is unable to compile extern __inline__ functions, and thus the Linux kernel. I found this bug as I tried to compile Linux 2.4.21-rc2, where the linker failed to find the extern __inline__ rtnetlink_rcv_skb(struct sk_buff) funktion in /usr/src/linux/net/core/rtnetlink.c, although it was implemented in the same module. I then wrote a little test program which causes gcc to fail: extern __inline__ void print_hello() { printf("Hello, World!\n"); } main() { print_hello(); } gcc then writes this to stderr: /tmp/ccX11xji.o(.text+0x11): In function `main': : undefined reference to `print_hello' collect2: ld returned 1 exit status Surprisingly it worked once I declared print_hello either extern or __inline__, only the combination did not work. I attached a tarball including the test.c, test.i, test.s, test.o and test.stderr.txt, the output that gcc -v --save-temps test.c wrote to stderr. I hope this helps. Florian Knauf >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/gzip; name="test.tar.gz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="test.tar.gz" H4sIAJaqyD4AA+1XT28bRRTfJKWtV0ICLghxYHBb1VG8613bsVtTV0CaphWhQNWWC5I7uzvenbI7 a3ZmHacIgdQLfAsO3PgCSBzhwvcAiQMHuCOFN/vHXrspToQSVGl/SjL73vvNzpv39r2ZCMKFbisn CsM0jE67rRiGYXY3jeKYwGx1FKPb6TTNZrPbNVJ+S0HGybqVIuYCRwgpe/G/85bZn1OQiSARQ4MB ZT5lZDBA45A6aBRRJgYe8f2wto4+T+VhrXpLauro4zDynTc/YdX1t9AXaoApm7HyWdLyf++uxDII Wf/0ZNdYVv/NWf23u812wu+W9X8quIBMVE0+AruqJsI1K6a+0Ci7nivsMAgwc5BsELkyn1L2j+cb SR7Dk11jSf2bzc32Yv2bRrOs/9PAl9u7N1dWVqbyirKmrBTs32ZjO/lbUyrKWeX+N789+eP8k1// /EHq1n/+/e+Dg4NfflKUna2tHqrt3Lm/jlp6C9VuEItitq4oOt8PBLZgFFE6evlTRHxdQBdRdAcL rOgW54ouOw5h4hj7eCPxXQHvZv6+WrCfycbX4bdS0H+3qijnYTyXzZc8KV/K5LWMt7uwXv6+jYy/ jGdk71MKvNcKcm57ufAuCQK/Vw/hyXG1oD8PwleZL2ezdV9S0r0W3/f16uHrLqKoP6P8dVC0rS3M WptbQcpnFuQXEr8kZE5egfkvFuzSz7QR2Yo8C5TCOSBNMiar557haIn/hCTs/GTXWHb/a3XMp/t/ u+z/p4GKPqQ+qUzvc5WkGau664eWj2Q1StX+iFTkcx29PYyZLWjIkltbT62MYu75lUvEGqmVIBzL Rz6qo1TBY8uvXLwiRQ4iXCJB1MxOrkgmXDSkiCcZXT7mdhv7fqXQDdSKT/CYqJWICPCL08e5X7qW +UodODgq1WccRdXySjmPtP6FQ6JIF5PjnLhHx5L6b7Wfuv+Z3a5Z1v9p4C7BDmUu4iNiczSMwgA1 Yh41fGo1XNvW5EhbVzrwwOJJA2qpkVDV90I2pG4cURIJFFDRQ7re4JHdsDMDQdoYaRph2PKJ5mPm xtglvG/X7Y2N+iM8xvVht1sfYQ5VXg+tR3YdO7guIkIkGaaOIjKkk770ByT5LyiNEqnBPRyRBmhA T9kwXDBIFVj2qPA0dzIBiu3HDtGmtEzRAE/klmZuJvOdfC7f54IE2mMIwozCfJ7Zw1jkr3Y0lwjZ OWe8wcCe4AEGJS1obT+E7ZK+y+KZ0iFW7M5EGRvNtftWSLxgQY33RH8y54+MHLDRLEvqPS+CtKIg dIjfQ6OQ04kqk/mARBxa91xHVJfm27ZNpG0j7bOYEpEk9cZgAJ11azDot2bC+7fvfHB3XvXhO/e2 bu1uP9jeBb2B0jMmHajKqO0JNA4jDxJLGOEI3HtMQMsoRz+meZp5kgX6e7RHIwdRl4XJp6deyAyo qut6FXGCI9tDsqgFRx6JSG9GuQaU64dSsiDI3OQrLQ/MPDGXtpmDwmG+ik9hs0eM8RA++FEU2oRz +AbTME3D7sTByMKc5FHUcDyZypCVLLVamBK4ChlAW2h8SMpRbbb6OhyyYTCCO4CDrH307Em6urOz BdGCiueC2rwnCxRHOECua2sBZRqZjCCT/U77KYtH8Eie1WDbNK6oCEMFPUDaR/tTd+e8xrD/AD7t aOpIUzfb+lVDN3RzznkUc9m83r1541BqEw4XY9PYROke5O4au0mFLE9I6PvEFk1ZZ542hN0QzXOg DwWI+MOBZENO9hkOqJzPPgVvk/f5TvoWnYd6c+ky0DPTHzsSJkThOHx6BD7QLOJSBlRtdwl5OWO6 fJ40zQdi+ndAPHiwF1VHcJAw55g7h+2oqQe15Lq6YUxMc72HbjOUX0/RQ3kfvNxTeyiG9jKkDD5w OE+g2pkNRROih4V75WU1z3cP+ZIn4khOMFHSvaFViJiXV8cSJUqUKFGiRIkSJUo81/gH3n4AXQAo AAA=
reply other threads:[~2003-05-19 10:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030519095848.27211.qmail@sources.redhat.com \ --to=i-sys@gmx.net \ --cc=gcc-gnats@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).