Skip to content

[clang] Document the return value of __builtin_COLUMN #118360

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 13, 2024
Merged

Conversation

GeorgeKA
Copy link
Contributor

@GeorgeKA GeorgeKA commented Dec 2, 2024

PR for issue #78657

Updated clang/docs/LanguageExtensions.rst to detail the return value of __builtin_COLUMN for this implementation.

--

Fyi, this is my first contribution, so please bear with me.

There already appears to be a unit test for __builtin_COLUMN in clang/test/SemaCXX/source_location.cpp.

PR for issue llvm#78657

Updated clang/docs/LanguageExtensions.rst to detail the return value of
__builtin_COLUMN for this implementation.
Copy link

github-actions bot commented Dec 2, 2024

Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

@llvmbot llvmbot added the clang Clang issues not falling into any other category label Dec 2, 2024
@GeorgeKA
Copy link
Contributor Author

GeorgeKA commented Dec 2, 2024

@frederick-vs-ja, were you looking for specific wording for source_location()::current().column(), or does this cover it?

@llvmbot
Copy link
Member

llvmbot commented Dec 2, 2024

@llvm/pr-subscribers-clang

Author: None (GeorgeKA)

Changes

PR for issue #78657

Updated clang/docs/LanguageExtensions.rst to detail the return value of __builtin_COLUMN for this implementation.

--

Fyi, this is my first contribution, so please bear with me.

There already appears to be a unit test for __builtin_COLUMN in clang/test/SemaCXX/source_location.cpp.


Full diff: https://github.com/llvm/llvm-project/pull/118360.diff

1 Files Affected:

  • (modified) clang/docs/LanguageExtensions.rst (+5-1)
diff --git a/clang/docs/LanguageExtensions.rst b/clang/docs/LanguageExtensions.rst
index 3c9078bcdf8118..00466fd2e7f020 100644
--- a/clang/docs/LanguageExtensions.rst
+++ b/clang/docs/LanguageExtensions.rst
@@ -4514,9 +4514,13 @@ default member initializer, the invocation point is the location of the
 constructor or aggregate initialization used to create the object. Otherwise
 the invocation point is the same as the location of the builtin.
 
-When the invocation point of ``__builtin_FUNCTION`` is not a function scope the
+When the invocation point of ``__builtin_FUNCTION`` is not a function scope, the
 empty string is returned.
 
+The builtin ``__builtin_COLUMN`` returns the offset from the start of the line,
+beginning from column 1. `This may differ from other implementations.
+<https://en.cppreference.com/w/cpp/utility/source_location/column>`_
+
 The builtin ``__builtin_source_location`` returns a pointer to constant static
 data of type ``std::source_location::__impl``. This type must have already been
 defined, and must contain exactly four fields: ``const char *_M_file_name``,

@GeorgeKA
Copy link
Contributor Author

GeorgeKA commented Dec 2, 2024

I don't have write permission, so requesting review via comment. Please and thanks:
@cor3ntin
@frederick-vs-ja

@GeorgeKA
Copy link
Contributor Author

GeorgeKA commented Dec 9, 2024

Any thoughts about this @frederick-vs-ja ?

@frederick-vs-ja, were you looking for specific wording for source_location()::current().column(), or does this cover it?

Comment on lines 4521 to 4523
beginning from column 1. `This may differ from other implementations.
<https://en.cppreference.com/w/cpp/utility/source_location/column>`_

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cor3ntin cor3ntin merged commit 473e251 into llvm:main Dec 13, 2024
7 checks passed
Copy link

@GeorgeKA Congratulations on having your first Pull Request (PR) merged into the LLVM Project!

Your changes will be combined with recent changes from other authors, then tested by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR.

Please check whether problems have been caused by your change specifically, as the builds can include changes from many authors. It is not uncommon for your change to be included in a build that fails due to someone else's changes, or infrastructure issues.

How to do this, and the rest of the post-merge process, is covered in detail here.

If your change does cause a problem, it may be reverted, or you can revert it yourself. This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again.

If you don't get any reports, no action is required from you. Your changes are working as expected, well done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clang Clang issues not falling into any other category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants