llvmbot wrote:
/pull-request llvm/llvm-project#101663
https://github.com/llvm/llvm-project/pull/101005
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
AaronBallman wrote:
> We could add similar clarifications to the release notes, which were
> initially included in an earlier version of this patch. So same question how
> we would need to approach that.
In terms of updating the release notes, once the cherry-pick happens, there's
an automate
https://github.com/AaronBallman milestoned
https://github.com/llvm/llvm-project/pull/101005
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
AaronBallman wrote:
We have instructions at
https://www.llvm.org/docs/GitHub.html#backporting-fixes-to-the-release-branches
but the basic gist of it is to add a special comment and add the PR to the
correct milestone. As in:
/cherry-pick 48d4d4b641702bf6db03a1bac73b7e13dea28349
https://githu
sjoerdmeijer wrote:
> LGTM, let's go ahead and merge this and get it backported to 19.x, thank you!
Thanks for your help with this.
I am mostly unfamiliar with the release process. Do you know how we can achieve
this? Do we suggest this commit to the release manager for a backport and
cherry
https://github.com/sjoerdmeijer closed
https://github.com/llvm/llvm-project/pull/101005
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/AaronBallman approved this pull request.
LGTM, let's go ahead and merge this and get it backported to 19.x, thank you!
https://github.com/llvm/llvm-project/pull/101005
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://l
sjoerdmeijer wrote:
@AaronBallman, shall we merge this?
https://github.com/llvm/llvm-project/pull/101005
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/jyknight approved this pull request.
LGTM, thanks.
https://github.com/llvm/llvm-project/pull/101005
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/Endilll approved this pull request.
https://github.com/llvm/llvm-project/pull/101005
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -429,8 +429,12 @@ 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
@@ -429,8 +429,12 @@ 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
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/AaronBallman commented:
FWIW, I'm happy enough with the proposed wording (I want to give others a
chance to weigh in before approving though).
https://github.com/llvm/llvm-project/pull/101005
___
cfe-commits mailing list
cfe-commits
https://github.com/sjoerdmeijer updated
https://github.com/llvm/llvm-project/pull/101005
>From 22f2e40c6d44c562e97162f04dee055a1be57460 Mon Sep 17 00:00:00 2001
From: Sjoerd Meijer
Date: Mon, 29 Jul 2024 19:31:18 +0530
Subject: [PATCH] Ofast documentation deprecation clarifications
Following u
15 matches
Mail list logo
