-
Notifications
You must be signed in to change notification settings - Fork 273
No rtti headers #477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
No rtti headers #477
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift
🧩 Analysis chain
🏁 Script executed:
Repository: NVIDIA/cudnn-frontend
Length of output: 11437
🏁 Script executed:
Repository: NVIDIA/cudnn-frontend
Length of output: 11437
🌐 Web query:
site:cmake.org/cmake/help/latest add_compile_options target_compile_options directory COMPILE_OPTIONS initialized target💡 Result:
In CMake, compile options can be managed at different scopes, ranging from directory-wide to target-specific, using the following mechanisms: add_compile_options The add_compile_options command operates at the directory scope [1][2]. It adds options to the COMPILE_OPTIONS directory property [1]. These options are automatically applied to all targets created within that directory and any subdirectories processed afterward [1]. target_compile_options The target_compile_options command operates at the target scope [3][2]. It adds options to the COMPILE_OPTIONS and/or INTERFACE_COMPILE_OPTIONS target properties of a specific target [3][4]. This command requires a scope keyword (PRIVATE, PUBLIC, or INTERFACE) to determine whether the options should only apply to the target itself (PRIVATE), be propagated to consumers (INTERFACE), or both (PUBLIC) [3][4]. Initialization and Property Relationships The COMPILE_OPTIONS target property is initialized using the current value of the COMPILE_OPTIONS directory property at the time the target is created [5][6]. Once a target is created, the directory-level options and the target-level options are distinct; subsequent changes to the directory property will not affect existing targets [5]. When building a target, the final set of compile options consists of the target's own COMPILE_OPTIONS property (which includes its initial directory-based options plus any added via target_compile_options(PRIVATE/PUBLIC)) and the INTERFACE_COMPILE_OPTIONS properties propagated from its dependencies [5][7][4].
Citations:
🌐 Web query:
site:learn.microsoft.com MSVC D9025 overriding /GR- /GR /WX warning💡 Result:
The MSVC compiler warning D9025 (overriding 'option1' with 'option2') occurs when conflicting command-line options are provided [1][2]. In the case of /GR and /GR-, these options are mutually exclusive: /GR enables Run-Time Type Information (RTTI), while /GR- disables it [3][4]. The compiler resolves this conflict by using the option that appears farthest to the right on the command line [1]. If both are specified, the one encountered last overrides the previous one [1]. Common causes for this warning include: 1. Conflicting Project Settings: The options may be defined in different places, such as the project's global C/C++ property pages and a specific source file's individual properties [1]. 2. Command Line Arguments: Build systems or manual command lines might inadvertently include both flags [1]. 3. Preprocessor or Build Tools: Generated build files (e.g., from CMake) may include conflicting configurations [5]. To resolve this: - Examine the compiler's Command Line property pages to see the full list of options applied [1]. - Check for redundant or contradictory settings in the C/C++ Language property page of your project [1][3]. - If you are using a build system like CMake, verify the configuration to ensure the desired RTTI setting is applied consistently across the project [5]. - If you need to override a project-wide setting, check the Additional Options field in the Command Line property page; adding the desired flag there will place it later on the command line, effectively overriding previous settings [1][6]. Note that /WX (Treat Warnings as Errors) is a separate flag that causes the compiler to treat all warnings as errors, which may cause your build to fail if a D9025 warning is generated [2]. You must resolve the underlying option conflict to prevent the D9025 warning, which in turn will resolve the /WX failure [1][2].
Citations:
🏁 Script executed:
Repository: NVIDIA/cudnn-frontend
Length of output: 520
Remove the inherited
/GR-from_compiled_module.When
CUDNN_FRONTEND_ENABLE_RTTI=OFFon MSVC, the target receives both/GR-and/GR. MSVC emits D9025, and/WXcan fail the build. Scope/GR-to non-Python targets or remove it from the Python directory before creating_compiled_module.📍 Affects 2 files
CMakeLists.txt#L13-L15(this comment)python/CMakeLists.txt#L75-L81🤖 Prompt for AI Agents
Source: MCP tools