This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Exporting new libgomp functions

From: Ian Lance Taylor <iant at google dot com>
To: Amittai Aviram <amittai dot aviram at yale dot edu>
Cc: gcc-help at gcc dot gnu dot org
Date: Wed, 12 Jan 2011 22:31:42 -0800
Subject: Re: Exporting new libgomp functions
References: <F0C0C8B6-7B69-443A-9B12-984F82A98CC5@yale.edu> <mcry66quezc.fsf@google.com> <3F451FD7-41C8-4739-9FF0-AB2ECB6B6520@yale.edu> <mcrd3o1vjtt.fsf@google.com> <240334EA-B598-4CF4-8854-E780063FCE15@yale.edu> <mcr4o9dviss.fsf@google.com> <03862729-2A73-49EB-AF0C-61ED7EBD3D09@yale.edu> <mcrmxn5tyui.fsf@google.com> <F3DAB457-0514-472A-8C43-11F8E64DB533@yale.edu>

Amittai Aviram <amittai.aviram@yale.edu> writes:

> What about omp.h.in?  I see that it has the standard omp function names listed in a particular syntax.  Am I supposed to edit that file manually?  Or does something else generate it?  Or can I create another *.h.in file alongside it?

No, that's just a header file.  It should not affect which symbols go
into the library.

Ian

References:
- Exporting new libgomp functions
  - From: Amittai Aviram
- Re: Exporting new libgomp functions
  - From: Ian Lance Taylor
- Re: Exporting new libgomp functions
  - From: Amittai Aviram
- Re: Exporting new libgomp functions
  - From: Ian Lance Taylor
- Re: Exporting new libgomp functions
  - From: Amittai Aviram
- Re: Exporting new libgomp functions
  - From: Ian Lance Taylor
- Re: Exporting new libgomp functions
  - From: Amittai Aviram
- Re: Exporting new libgomp functions
  - From: Ian Lance Taylor
- Re: Exporting new libgomp functions
  - From: Amittai Aviram

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]