public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Andrew Zabolotny" <bit@freya.etu.ru>
To: "egcs@cygnus.com" <egcs@cygnus.com>
Subject: egcs-1.0 on mingw32/possibly cygwin32 regression
Date: Thu, 08 Jan 1998 01:44:00 -0000	[thread overview]
Message-ID: <199801080945.MAA20705@freya> (raw)

Hello everybody!

The mingw32 egcs-1.0 port and possibly cygnus-win32 egcs-1.0 (since first
is
heavily based on second) has the following problem:

The program:

---------------
#include <stdio.h>

static __attribute__ ((stdcall)) BlackHole(int a);

void doit()
{
 BlackHole(1);
}

static __attribute__ ((stdcall)) BlackHole(int a)
{
 printf("disappearing function! %d\n", a);
}

int main()
{
 doit();
 return (0);
}
---------------

does not compile correctly with -O3. However, it compiles okay if the
-fkeep-inline-functions or with -fno-inline-functions switch was
specified.
The problem is that the BlackHole function is for some reason marked
as 'inline' but instead of inlining its code the compiler puts a
'call BlackHole@4' anyway, but the actual function code is totally
missing.

This problem is not present with gcc-2.7.2 from cygwin32.

I've did not tracked the problem, but I think it's related to the
ENCODE_SECTION_INFO macro in cygwin32.h (the name of function changes
and compiler detects by name whenever the function is inline??? nonsense)

Greetings,
    _\ndy@teamOS/2


             reply	other threads:[~1998-01-08  1:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-08  1:44 Andrew Zabolotny [this message]
1998-01-09 20:45 ` [patch] " Mumit Khan
1998-01-14  4:17   ` Jeffrey A Law

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=199801080945.MAA20705@freya \
    --to=bit@freya.etu.ru \
    --cc=egcs@cygnus.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: 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).