Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
dumux
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
dumux-repositories
dumux
Commits
9aa3304b
Commit
9aa3304b
authored
9 years ago
by
Christoph Grüninger
Browse files
Options
Downloads
Patches
Plain Diff
Remove guard for GCC < 4.5 which is unsupported anyway
parent
7de53a3e
No related branches found
No related tags found
1 merge request
!43
Feature/valgrind with cmake
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
dumux/common/valgrind.hh
+0
-15
0 additions, 15 deletions
dumux/common/valgrind.hh
with
0 additions
and
15 deletions
dumux/common/valgrind.hh
+
0
−
15
View file @
9aa3304b
...
...
@@ -23,21 +23,6 @@
#ifndef DUMUX_VALGRIND_HH
#define DUMUX_VALGRIND_HH
#ifndef __clang__
#if __GNUC__ < 4 || (__GNUC__ == 4 && __GNUC_MINOR__ < 5)
// do not do static_asserts for gcc < 4.5 (semantics changed, so old
// GCCs will complain when using static_assert)
# define static_assert(a, b)
// do not do valgrind client requests for gcc < 4.5 (old GCCs do not
// support anonymous template arguments which results in errors for
// BoundaryTypes)
# ifdef HAVE_VALGRIND
# undef HAVE_VALGRIND
# endif
#endif // GCC < 4.5
#endif // __clang__
#ifndef HAVE_VALGRIND
// make sure that the HAVE_VALGRIND macro is always defined
# define HAVE_VALGRIND 0
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment