Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
llvm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tracing-llvm
llvm
Commits
cb6592cf
Commit
cb6592cf
authored
8 years ago
by
Matt Arsenault
Browse files
Options
Downloads
Patches
Plain Diff
Add some 5.0 release notes
Note speculatable and alloca address space change. llvm-svn: 308482
parent
03601601
Loading
Loading
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
llvm/docs/ReleaseNotes.rst
+7
-1
7 additions, 1 deletion
llvm/docs/ReleaseNotes.rst
with
7 additions
and
1 deletion
llvm/docs/ReleaseNotes.rst
+
7
−
1
View file @
cb6592cf
...
...
@@ -71,6 +71,12 @@ Non-comprehensive list of changes in this release
Changes to the LLVM IR
----------------------
* The datalayout string may now indicate an address space to use for
the pointer type of alloca rather than the default of 0.
* Added speculatable attribute indicating a function which does has no
side-effects which could inhibit hoisting of calls.
Changes to the ARM Backend
--------------------------
...
...
@@ -96,7 +102,7 @@ Changes to the X86 Target
Changes to the AMDGPU Target
-----------------------------
During this release ...
* Initial gfx9 support
Changes to the AVR Target
-----------------------------
...
...
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