From clangd-dev at lists.llvm.org Wed Jan 12 10:29:53 2022
From: clangd-dev at lists.llvm.org (Tanya Lattner via clangd-dev)
Date: Wed, 12 Jan 2022 10:29:53 -0800
Subject: [clangd-dev] clangd-dev mailing list moving to LLVM Discourse
Message-ID: <9F21E73B-6B93-4C93-9FFC-149CFF774EDA@llvm.org>
The clangd-dev mailing list will be moved to LLVM Discourse under the “clangd” category (under Clang Frontend). All archives will be migrated. This list will be no longer be in use starting February 1, 2022. Please see this blog post for all details: https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/
If you would like to continue to get notifications regarding clangd, you must do the following:
1) Sign up for an account on LLVM Discourse (you may use your GitHub account):
https://llvm.discourse.group/
Note: If you are attempting to sign up after the mailing list archives have been migrated to Discourse (Feb 1), you may find that an account has been created for the email you used on the LLVM mailing list. If this is the case, click “Forgot password” to get access to this account.
2) Sign up for notifications to the “clangd" category.
Click on the “clangd" category:
Click on the bell icon to set notifications. You can also modify these in your Account->Preferences->Notifications.
Thanks,
Tanya Lattner
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Image 1-12-22 at 10.24 AM.jpeg
Type: image/jpeg
Size: 37422 bytes
Desc: not available
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Image 1-12-22 at 10.26 AM.jpeg
Type: image/jpeg
Size: 23784 bytes
Desc: not available
URL:
From clangd-dev at lists.llvm.org Sat Jan 29 08:21:34 2022
From: clangd-dev at lists.llvm.org (Tanya Lattner via clangd-dev)
Date: Sat, 29 Jan 2022 08:21:34 -0800
Subject: [clangd-dev] Mailman->Discourse Migration on February 1, 10am PST
Message-ID: <6B90B043-DD04-4D39-A467-191AF3DDF5C8@llvm.org>
LLVM Community,
As referenced in this blog post , we are getting close to the deadline for migration for some Mailman lists to Discourse. If you are receiving this email from a LLVM Mailman list, then this list will be migrating to Discourse on February 1st.
We have gone through several test runs and feel that we are ready to do the final migration on February 1st starting at 10 am PST. Once the migration begins, the impacted Mailman lists and Discourse will be read only until it has completed.
Here are the steps of the migration process on February 1st at 10 am PST:
The Mailman lists that are migrating will be placed in “read-only” mode. No mail will be accepted to the list.
Mailman will be shut down while the final archives are collected. We expect this downtime to be about 15 minutes.
The mailman archives are sent to Discourse for migration (15-20 minutes for data transfer).
The LLVM DIscourse is put into read-only mode. Given the size of our archives, we expect the import to take 5 hours.
Sanity-checks will be made to ensure that everything looks as expected. We estimate this will take 1 hour or less.
The LLVM Discourse will be opened up again with all the archives imported.
We will post on Discourse about how things went and any next steps in the “Announcements” category.
We will use the Discourse Migration website to communicate where we are in the process.
We expect the LLVM Discourse to open by 5pm PST, but realize that even in the best plans, there may be unexpected situations that arise that cause the migration to take longer or possibly be stopped. If that occurs, we will evaluate the best course of action and communicate to the community as described above.
If you have any questions, please let me know.
Thanks,
Tanya
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From clangd-dev at lists.llvm.org Wed Jan 26 00:49:52 2022
From: clangd-dev at lists.llvm.org (=?UTF-8?Q?Benedikt_Wei=c3=9f?= via clangd-dev)
Date: Wed, 26 Jan 2022 09:49:52 +0100
Subject: [clangd-dev] #line directives not considered in clangd
Message-ID: <8c638129-d6e0-8bdf-e37c-3d7bcc768f48@gmail.com>
Hello,
I am currently using the clangd for writing my own language server
implementation for a new programming language, let's call it newlang.
In this new programming language, it is possible to write C++ source
code in specific places, so it is possible to embed C++ code in specific
syntax constructs. Afterwards the files are compiled to C++ to use the
normal C++ toolchain.
As you can imagine, the embedded C++ from the original file is now also
contained in the generated C++ file but in other places (at other line
numbers etc because of additional generated C++ code). So, the embedded
C++ source code which was at, for example, line 52 (in the original file
of the new programming language) is now at line 132 in the generated C++
file.
To generate meaningful compiler messages, those places in the C++ file
are annotated with #line directives which link back to the original file
because you do not want to edit and analyze *generated* files but the
original source file in the new programming language.
So, if I am using the standalone clang compiler, everything is correct
and as expected:
benedikt at fedora:~$ clang /path/to/example_file.cxx
/path/to/example_file.newlang:39:9: warning: expression result unused
[-Wunused-value]
because of something like
#line 22 "/path/to/example_file.newlang"
in the generated example_file.cxx. This is correct because the
example_file.cxx is generated from the example_file.newlang and "links
back" to the original location of the C++ source code, via those #line
directives.
Now my question is: How can I get the *clangd* to recognize/consider
#line directives? I could not get it to work. clangd seems to ignore
them. clangd compiles the file correctly and generates
"publishDiagnostics" with the same warning and error messages etc but
without considering the #line directives, it only considers the line
numbers from the C++ file (in this example_file.cxx it would be like
line 132).
I also tried "-fuse-line-directives" but without success.
Thanks you for your time.
With kind regards,
Benedikt Weiß