sjoerdmeijer wrote:
> I think we need these changes to be against main and not 19.x, aside from the
> release notes (otherwise we're losing the documentation in 20.x).
Oh right, yes, missed that, makes sense. Will split this up, let's do the
documentation update here first as suggested.
htt
https://github.com/AaronBallman commented:
Thank you for working on this!
I think we need these changes to be against `main` and not `19.x`, aside from
the release notes (otherwise we're losing the documentation in 20.x). For the
release notes, I think we can talk to @tstellar and @tru about g
@@ -495,10 +495,12 @@ New Compiler Flags
Deprecated Compiler Flags
-
-- The ``-Ofast`` command-line option has been deprecated. This option both
- enables the ``-O3`` optimization-level, as well as enabling non-standard
- ``-ffast-math`` behaviors. As
@@ -429,8 +429,11 @@ Code Generation Options
:option:`-Ofast` Enables all the optimizations from :option:`-O3` along
with other aggressive optimizations that may violate strict compliance with
-language standards. This is deprecated in favor of :option:`-O3`
-i
https://github.com/AaronBallman edited
https://github.com/llvm/llvm-project/pull/101005
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Sjoerd Meijer (sjoerdmeijer)
Changes
Following up on the RFC discussion, this is clarifying that the main purpose
and effect of the -Ofast deprecation is to discourage its usage and that
everything else is more or less open for discussion
https://github.com/sjoerdmeijer created
https://github.com/llvm/llvm-project/pull/101005
Following up on the RFC discussion, this is clarifying that the main purpose
and effect of the -Ofast deprecation is to discourage its usage and that
everything else is more or less open for discussion, e.
