[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mkoctfile and OpenMP
From: |
Kai Torben Ohlhus |
Subject: |
Re: mkoctfile and OpenMP |
Date: |
Sun, 10 May 2020 16:48:07 +0900 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 |
On 5/9/20 10:09 PM, José Luis García Pallero wrote:
> Hello:
>
> I've observed in Octave 5.2.0 (I don't know if it was present in
> previous versions) that mkocfile by default activates the OpenMP
> compatibility. Which is the reason for this behavior instead of the
> use of -fopenmp by the user as in gcc?
>
mkoctfile is a wrapper for the system compiler (e.g. "gcc").
mkoctfile -p CC
gcc
Do you refer to the standard compiler flags of "mkoctfile", i.e., why is
"-fopenmp" set by default?
mkoctfile -p ALL_CFLAGS
-I/usr/include/octave-5.2.0/octave/..
-I/usr/include/octave-5.2.0/octave -pthread -fopenmp -g -O2
Is there a reason not to use this flag by default?
Kai
- mkoctfile and OpenMP, José Luis García Pallero, 2020/05/09
- Re: mkoctfile and OpenMP,
Kai Torben Ohlhus <=