Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
GIMP
GIMP
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,761
    • Issues 2,761
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 37
    • Merge Requests 37
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • GIMPGIMP
  • Issues
  • #5053

Closed
Open
Opened May 08, 2020 by Lloyd Konneker@bootchkContributor

meson build with buildtype=release causes g-ir_scanner dies with SIGILL on AMD machine

GIMP version: 2.99

Operating System: Ubuntu 19.10

Package: self built, the problem is in the meson build.

Description of the bug

Building gimp with meson with buildtype=release seems to crash g-ir-scanner (?) and stop the build, whereas buildtype=debug does not.

Reproduction

Is the bug reproducible? Always

Reproduction steps:

    cd /home/gimp
    meson _build \
     --buildtype=release \
     -Djavascript=never \
     -Dlua=never \
     -Dpython=always \
     -Dgtk-doc=false
    cd _build
    ninja
    ninja install

yields:

Command '['/home/gimp/_build/tmp-introspectnrkd9xnk/Gimp-3.0', '--introspect-dump=/home/gimp/_build/tmp-introspectnrkd9xnk/functions.txt,/home/gimp/_build/tmp-introspectnrkd9xnk/dump.xml']' died with <Signals.SIGILL: 4>.

Just preceding that was:

/usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 .......

Expected result: build completes

Actual result: build stops

Additional information

The workaround is: don't do that, use buildtype=debug. I know the meson build is experimental.

SIGILL is illegal instruction. Some tool is executing an illegal instruction?

gegl#190 (closed) seems pertinent. Possibly related to SMD instructions invoked when compiler is optimizing?

My hw is an older AMD Phenom.

I am building inside a vagga container, I haven't tested it outside the container.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/gimp#5053