Package Details: openfoam-org 12.20250206-8

Git Clone URL: https://aur.archlinux.org/openfoam.git (read-only, click to copy)
Package Base: openfoam
Description: The open source CFD toolbox (www.openfoam.org)
Upstream URL: http://www.openfoam.org
Licenses: GPL-3.0-or-later
Provides: openfoam
Submitter: None
Maintainer: envolution
Last Packager: envolution
Votes: 66
Popularity: 1.34
First Submitted: 2009-07-02 09:16 (UTC)
Last Updated: 2025-06-11 06:13 (UTC)

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 31 Next › Last »

disc-kuraudo commented on 2020-02-18 09:45 (UTC) (edited on 2020-02-18 09:57 (UTC) by disc-kuraudo)

Yeah there's no need to split-package this as it will be built on the machine it will run on anyway, in contrast to tensorflow/tensorflow-opt that is in the main repositories and the binaries are distributed.

For people that don't want to waste time and resources/energy and set their /etc/makepkg.conf accordingly this change would improve the OpenFOAM performance.

For people that left the /etc/makepkg.conf untouched basically nothing changes (even the -O2 gets overridden by a -O3 that is already there in the cOpt/c++Opt file as it comes afterwards).

lahwaacz commented on 2020-02-18 09:03 (UTC)

Using flags specified in makepkg.conf is not actually about enabling optimizations by itself, but it allows users to configure whatever flags they want. For openfoam-opt you would have to actually force some specific flags, but that's unnecessary for a source-based repo like the AUR - users can change the pkgname themselves if they need.

petronny commented on 2020-02-18 08:55 (UTC) (edited on 2020-02-18 08:56 (UTC) by petronny)

So is the difference like the difference between tensorflow and tensorflow-opt? The 2nd one enables more instructions like AVX/AVX2.

Should I add an package called openfoam-opt like that?

disc-kuraudo commented on 2020-02-18 07:57 (UTC)

The default CFLAGS/CXXFLAGS set in the /etc/makepkg.conf are currently

-march=x86-64 -mtune=generic -O2 -pipe -fno-plt

With this it will sort of run on every x86-64 (amd64) machine.

Usually build tools like GNU Autotools, CMake etc. will automatically include the values set in the environment variables like that in the build process. OpenFOAM with this special WMake build tool apparently doesn't do so.

For my Desktop PC I changed the makepkg.conf CFLAGS/CXXFLAGS line to

-march=znver2 -mtune=znver2 -O3 -pipe -fno-plt

so it enables all the AVX/AVX2/FMA3 SIMD instructions when building packages which is for my Zen 2 AMD CPU and that will improve the performance for scientific computations a lot.

Can check and see what the default flags for compilation with GCC are with

gcc -Q --help=target | grep "march\|mtune\|sse\|avx\|fma"

It basically sets back to very basic Pentium 4 era SSE2 SIMD instructions and use none the instruction set extensions "recent" CPUs have implemented.

https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html

petronny commented on 2020-02-18 05:13 (UTC)

@daren Will the binaries be still compatible with old machines after applying your changes?

disc-kuraudo commented on 2020-02-12 13:17 (UTC) (edited on 2020-02-12 14:00 (UTC) by disc-kuraudo)

The CXXFLAGS environment variable set in makepkg.conf don't seem to be picked up in the build system.

How could these be used so it doesn't create binaries that only contain 20 year old amd64 instructions? There's no -march flag whatsoever in the compile commands.

Edit: Setting this in the build() function before building works.

  # Apply CFLAGS and CXXFLAGS to compile options
  sed -e "s/\(cOPT.*=\)/\1 ${CFLAGS}/g" \
      -i ${srcdir}/${_distpkgname}-${pkgver}/wmake/rules/linux64Gcc/cOpt
  sed -e "s/\(c++OPT.*=\)/\1 ${CXXFLAGS}/g" \
      -i ${srcdir}/${_distpkgname}-${pkgver}/wmake/rules/linux64Gcc/c++Opt

petronny commented on 2019-08-28 04:55 (UTC)

@ng0177 Well, we can't help you if there is no log or output. I have no idea what the MPI error is.

lahwaacz commented on 2019-08-27 14:52 (UTC)

@ng0177 Manjaro is not supported here. Install Arch Linux.

ng0177 commented on 2019-08-26 13:01 (UTC)

V7 builds fine on a Manjaro Desktop but on a Manjaro Laptop it fails w/ an MPI error. Any ideas?

petronny commented on 2019-04-29 05:09 (UTC)

paraview-opt can also be downloaded from arch4edu now.

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 31 Next › Last »