public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tim Prince <timothyprince@sbcglobal.net>
To: Thomas Yeh <tomyeh@CS.UCLA.EDU>
Cc: gcc-help@gcc.gnu.org
Subject: Re: openmp support
Date: Thu, 01 Jun 2006 12:06:00 -0000	[thread overview]
Message-ID: <447ED82D.60901@sbcglobal.net> (raw)
In-Reply-To: <Pine.GSO.4.58.0606010055030.12053@panther.cs.ucla.edu>

Thomas Yeh wrote:
> Hi All,
> 
>   According to the gcc news, gcc 4.X seems to support openMP. Can anyone
> point me to the libraries I need for both tru64 linux and x86 linux?
> 

Maybe I don't understand your question.  Inclusion of OpenMP in gcc-4.1 
isn't going to affect gcc-4.0.  Unless someone has tested gcc 4.1 on 
tru64, that part of the question seems moot.
On linux (32 bit?), reading the gcc build instructions should give you 
some clue about library updates which may be required on top of a 
reasonably current distro with gcc development components installed. 
For example, gmp with mpfr enabled would be needed for a full 
installation of gcc-4.1.  That might be there already if your distro 
includes gcc-4.0.

  reply	other threads:[~2006-06-01 12:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01  2:21 Problem when using gcc 4.1 + binutil 2.16.92 + glibc 2.4 + ARM EABI Fengwei Yin
2006-06-01  7:59 ` openmp support Thomas Yeh
2006-06-01 12:06   ` Tim Prince [this message]
2006-06-01 18:30     ` Thomas Yeh
2006-06-01 23:59       ` make error for development branch Thomas Yeh
  -- strict thread matches above, loose matches on Subject: below --
2006-06-01 21:30 Re: openmp support Timothy C Prince
2006-06-01 21:59 ` Thomas Yeh
2006-06-02  1:17   ` Tim Prince
1999-10-21 11:27 OpenMP support Eugen Dedu
1999-10-31 13:57 ` Eugen Dedu

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=447ED82D.60901@sbcglobal.net \
    --to=timothyprince@sbcglobal.net \
    --cc=gcc-help@gcc.gnu.org \
    --cc=tomyeh@CS.UCLA.EDU \
    --cc=tprince@myrealbox.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).