Address the comment. Delete the options.

It should be kept for compatibility. These three options may be used in other projects compiled by gcc.
Clang should ignore it.
https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html

Sorry about that I forgot to modify author information.

It looks like test is passed now. Although I don't know why http://lab.llvm.org:8011/builders/openmp-gcc-x86_64-linux-debian/builds/1710 fails.

LGTM.

@TH3CHARLie
I can commit this for you.
git commit --amend --author="What-is-your-name <What-is-your-email-address>" ?
If you are interested in obtaining commit right. please refer to https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access

You can refer https://llvm.org/docs/Phabricator.html#committing-a-change to commit a change.
If your commit message has Differential Revision: <URL>, the differential will close automatically.
arc patch D<Revision> is used to fetch a differential from Phabricator.
https://llvm.org/docs/Phabricator.html#committing-someone-s-change-from-phabricator

Do you plan to land this change?

LGTM.

@AlexanderLanin
git commit --amend --author="What-is-your-name <What-is-your-email-address>" ?

Could you add tests in llvm/unittests/ADT/TripleTest.cpp

LGTM.
But I have tried gnu size, and I found that has two blank lines between archive members.
Here only one blank line.
What's your opinion?

There shows "Context not available."
Please follow https://llvm.org/docs/Phabricator.html#requesting-a-review-via-the-web-interface to upload patch.

The testcases tools/llvm-size/archive.test, tools/llvm-size/multiple-inputs.test and tools/llvm-size/radix.test
fail due to this patch. Could you update this testcases? You can try to execute command "ninja check-all -j32".

There shows "Context not available".
Could you update for this?

LGTM.

This is fixed by https://reviews.llvm.org/rG437e0e5191ca255db27e86d232020844c1fd08c8.

Do you need someone to commit this change for you?

Could add "[NFC]" in the title.
That means "No Function Change".

It looks like some of changes are the same as this patch https://reviews.llvm.org/D71646.
Please based on https://reviews.llvm.org/D71646 this patch to make change.

This is fixed by https://reviews.llvm.org/rG002adabb3a251a81ef304353eefb1bf96ec388f6.

Could you add "[NFC]" in the title.
That means No Function Change.

Ok. Thanks

This patch is only for RISCV.
The title should have prefix "[RISCV]".

I think this checking should be implemented in lib/Sema/SemaChecking.cpp.

@j-carl Could you give a Python 3.8 syntax reference for this change.

A few nits.
You can use git-clang-format to format your patch for following llvm coding style.

If an instruction has side effects, it would be a scheduling barrier.
Not any instruction can be scheduled crossing it.

I have committed this patch for you.
If you are interested in obtaining the commit right. you can refer to https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access.

I am curious what is difference of code generation after applying your changes?

LGTM, I have verified it.

Link http://llvm.org/44239 is not available.

Hi, I can help to commit it for you.
You can obtain the commit right by following https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access.

I can commit it for you.
If you are interested in obtaining the commit right. you can refer https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access.

Do you need someone to commit this change for you?

This is fixed by https://reviews.llvm.org/rL345960

Do you need someone to commit this change for you?

Could you remove "[PATCH]" from the title?

Hi @ZhangKang
You may follow @lkail 's suggestion is fine.
I am not a PowerPC guy. Just give some suggestions.