[MacPorts] #58442: clang-7, 8.0 - seg. faults when used as assembler with assertions variant active.

MacPorts noreply at macports.org
Fri May 10 00:35:36 UTC 2019


#58442: clang-7,8.0 - seg. faults when used as assembler with assertions variant
active.
----------------------------------+--------------------
  Reporter:  mouse07410           |      Owner:  (none)
      Type:  defect               |     Status:  new
  Priority:  Normal               |  Milestone:
 Component:  ports                |    Version:
Resolution:                       |   Keywords:
      Port:  clang-7.0 clang-8.0  |
----------------------------------+--------------------

Comment (by mouse07410):

 > 'Doctor, doctor, it hurts when I do this' 'Then don't do that!'
 {{{
 - What are you looking for here under the lamppost?
 - My keys.
 - Did you lose them here?
 - No, over there.
 - Then why are you looking for them here?
 - Because it's dark there.
 }}}


 > You are using a non-standard variant which counts as a special build

 Since when did "non-default" become "non-standard"?

 Are you testing your ports for all the variants you define/support? Or
 only the default one?


 >
 > The build bots have all built gcc9 and gcc10 fine on macOS10.7+

 MacOS **10.7**?Are you validating under 10.14.x using Xcode-10.2.x? If
 not, I'd say that explains why you aren't catching this crash. Xcode-10.2
 is quite different in what it allows and what it fails than the previous
 versions, at least in my experience.

 Also, as I'm working with crypto code that tries to squeeze an extra bit
 of performance by utilizing inline assembly (I'm one of the maintainers of
 Crypto++ https://en.wikipedia.org/wiki/Crypto%2B%2B library), I'm trying
 to make sure it compiles with all the compilers available on MacOS. I
 noticed that the only way to get Macports GCC to compile with inline
 assembly is to make it invoke Xcode assembler via {{{-Wa,-q}}}. We're also
 using {{{export AS_INTEGRATED_ASSEMBLER=1}}}.
 I'd just stick with Xcode, but it's GCC sucks even more, and it's very
 outdated besides. So, for a decent GCC have to use Macports port.

 Here's my setup:
 {{{
 $ port installed llvm-8.0 clang-8.0 cctools ld64 gcc libgcc libgcc9
 libgcc8
 The following ports are currently installed:
   cctools @921_1+xcode (active)
   ld64 @3_1+ld64_xcode (active)
   clang-8.0 @8.0.0_0+analyzer+assertions+libstdcxx (active)
   libgcc @2.0_1 (active)
   libgcc8 @8.3.0_5 (active)
   libgcc9 @9.1.0_1 (active)
   llvm-8.0 @8.0.0_0+assertions+polly (active)
 $ port select --list gcc
 Available versions for gcc:
         mp-gcc8
         mp-gcc9 (active)
         none
 $ port select --list clang
 Available versions for clang:
         apple-clang (active)
         mp-clang-8.0
         none
 $ port select --list llvm
 Available versions for llvm:
         mp-llvm-6.0
         mp-llvm-8.0
         none (active)
 $ $ cat /opt/local/etc/select/clang/apple-clang
 -
 /usr/bin/clang++
 /usr/bin/clang
 -
 . . . . . [30 more lines "-"] . . . . .
 }}}

-- 
Ticket URL: <https://trac.macports.org/ticket/58442#comment:39>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list