public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Robert Oeffner" <robert@oeffner.net>
To: <gcc@gcc.gnu.org>
Subject: Porting GCC 4.4.0 to interix
Date: Thu, 30 Jul 2009 22:58:00 -0000	[thread overview]
Message-ID: <3CB8E75EFE6C4F3AA4353943C0C0E327@Dirac> (raw)

Hi,
I'm new to this mailing list and hope this is the right one I'm addressing.
Lately I have been trying to port gcc and g++ from GCC 4.4.0 to interix (the 
BSD-like unix subsystem optionally available for WinXP and Vista). The 
subsystem is shipped with gcc and g++ 3.3 and binutils 2.13 which I have 
used for the bootstrap. Based on other peoples patches I have had some 
success.

Until now there is no compiler available for interix that supports OpenMP 
and that's what I'm after. As libgomp in GCC so far isn't targeting interix 
I have made some changes to libgomp in my copy of the GCC 4.4.0 
distribution.  A new source file was created, 
gcc-4.4.0/libgomp/config/posix/interix/proc.c, which is templated on the 
existing gcc-4.4.0/libgomp/config/posix/proc.c and 
gcc-4.4.0/libgomp/config/posix/mingw32/proc.c in the distribution (see
 http://www.oeffner.net/stuff/gcc-4.4.0_interix_changes.zip
or http://www.suacommunity.com/forum/tm.aspx?m=16600 ). With this file and 
modifications to GCC configuration files in the distribution I can bootstrap 
GCC 4.4.0 to build gcc and g++ compilers to support OpenMP on interix.

Although small OpenMP C++ programs builds and runs just fine I have problems 
with a large program that also uses OpenMP. The large program is unstable 
and crashes when compiled with OpenMP on interix. Compiled with g++4.4.0 
without OpenMP it runs like a charm. As we distribute this program to other 
platforms like Linux, MacOSX and Win32 where it runs fine with OpenMP I 
believe that my current implementation I have for porting libgomp to interix 
is buggy.

If anyone knows about some common or obvious pitfalls when porting libgomp 
to a new platform or if anyone has got any advice about what not to do I'd 
be very grateful.

Many thanks,

Rob

 

             reply	other threads:[~2009-07-30 22:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 22:58 Robert Oeffner [this message]
2009-07-31  0:10 ` Ben Elliston

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=3CB8E75EFE6C4F3AA4353943C0C0E327@Dirac \
    --to=robert@oeffner.net \
    --cc=gcc@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).