Build fails with LTO #120444
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#120444
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I tried to build with the following *FLAGS to optimize the build:
-flto=4 -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing
Note the -Werror=* flags are used to help detect cases where the compiler tries to optimize by assuming UB cannot exist in the source code -- if it does exist, ordinarily the code would be miscompiled, and this says to make the miscompilation a fatal error.
I got this error:
Reported downstream: https://bugs.gentoo.org/859607
Build logs for 4.1.0 are attached.
I can confirm the fact that there is multiple structure declarations with the same name.... blender is ndr right now...
Hi, thanks for the report. For build failure and related questions, best to ask in #blender-builds or devtalk. They are not handled on tracker.
I have reported a bug in your source code whereby your source code contains buggy logic that violates the C++ One Definition Rule.
It's not a support question because I am not confused about how to build blender and I don't need guidance or help on doing so.
Fix your code (not the build, the code) or don't fix it, the matter is now out of my hands.
P.S.
It is quite something when one blender developer confirms that it is a valid bug in the source code and then another developer comes along and says "sorry, we don't handle support questions here, closed".
This could be something that we might want to take care for a little bit. Most of the errors here are regarding different definitions of structs that are in different files, which compiles fine because the compiler knows the scope of those definition and they didn't overlap. The problem with LTO is that the object file only contains the name for reference, so the optimizer will not know what type the reference is exactly.
A lot of those "same name multiple definitions" problem happens between legacy/current code. It's possible that we could change those names so no names will ever be the same across different files, but I'm not sure if it will make that much of a difference in performance by being able to use LTO.
Just dumping answer from chat : "a bunch of those are due to our
DNA_DEPRECATED_ALLOW
setup that messes with the structs, not a whole lot we can do about that"That true, this bug tracker is used for bugs which is strongly restricted as bugs for users which is download blender from https://www.blender.org/download/.
Issues in building blender (as issues with specific compilers) should be reported in other channels.
So, you can send whole report, or each case of error separated, in the chat: https://blender.chat/channel/core-module