Re: [PATCH v2 2/4] libgrust: Add libproc_macro and build system

2024-01-16 Thread Jason Merrill

On 12/15/23 04:53, Thomas Schwinge wrote:

Hi Jason!

I think you usually deal with these kind of GCC Git things?  If not,
please let me know.


I just took care of this; I didn't notice it until now because the 
subject line didn't seem relevant to me.



On 2023-10-26T10:21:18+0200, I wrote:

First, I've pushed into GCC upstream Git branch devel/rust/libgrust-v2
the "v2" libgrust changes as posted by Arthur, so that people can easily
test this before it getting into Git master branch.  [...]


Please now delete the GCC Git 'devel/rust/libgrust-v2' branch, which was
only used temporarily, and is now obsolete.

 $ git push upstream :devel/rust/libgrust-v2
 remote: *** Deleting branch 'devel/rust/libgrust-v2' is not allowed.
 remote: ***
 remote: *** This repository currently only allow the deletion of references
 remote: *** whose name matches the following:
 remote: ***
 remote: *** refs/users/[^/]*/heads/.*
 remote: *** refs/vendors/[^/]*/heads/.*
 remote: ***
 remote: *** Branch deletion is only allowed for user and vendor branches.  
If another branch was created by mistake, contact an administrator to delete it 
on the server with git update-ref.  If a development branch is dead, also 
contact an administrator to move it under refs/dead/heads/ rather than deleting 
it.
 remote: error: hook declined to update refs/heads/devel/rust/libgrust-v2
 To git+ssh://gcc.gnu.org/git/gcc.git
  ! [remote rejected]   devel/rust/libgrust-v2 (hook declined)
 error: failed to push some refs to 'git+ssh://gcc.gnu.org/git/gcc.git'


Grüße
  Thomas





[Bug rust/108111] Rust meets clang

2024-01-16 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108111

--- Comment #4 from GCC Commits  ---
The trunk branch has been updated by Arthur Cohen :

https://gcc.gnu.org/g:2046aec032f743023a5e353735255d951e2e54d6

commit r14-7347-g2046aec032f743023a5e353735255d951e2e54d6
Author: Marc Poulhiès 
Date:   Sat Dec 17 16:23:05 2022 +0100

gccrs: fix some clang warnings

This fixes some extra warnings reported by clang.

gcc/rust/ChangeLog:
PR rust/108111
* ast/rust-ast-full-decls.h (StructPatternElements): Declare as a
class.
* ast/rust-item.h (EnumItem): Mark several method as being
overrides.
* ast/rust-pattern.h (StructPattern::get_locus): Add override.
* lex/rust-lex.h (BufferInputSource): Use reference_wrapper
instead of bare reference.
(TokenSource::get): Add method to implement the reference_wrapper
interface.
* typecheck/rust-tyty.h (TypeBoundPredicate): Add empty dtor.
* util/rust-buffered-queue.h (peek): Source token stream is now
using a reference_wrapper, use .get()

Signed-off-by: Marc Poulhiès 

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug translation/108890] Translation mistakes 2023

2024-01-16 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108890

--- Comment #7 from GCC Commits  ---
The trunk branch has been updated by Arthur Cohen :

https://gcc.gnu.org/g:747d9a92ddb74fa7ba1bb6ca0079abd5eaa38791

commit r14-7504-g747d9a92ddb74fa7ba1bb6ca0079abd5eaa38791
Author: TieWay59 
Date:   Wed Apr 19 14:07:34 2023 +0800

gccrs: Fix translation mistakes 2023 in GCC/Rust [PR108890]

In https://gcc.gnu.org/PR108890 "Translation mistakes 2023"
@rillig lists several issues with GCC/Rust diagnostics and
option help texts (but also a few non-GCC/Rust).

This commit fix mistakes only related to GCC/Rust,
specifically to the file `gcc/rust/lang.opt`.

closes https://github.com/Rust-GCC/gccrs/issues/1916

PR translation/108890
gcc/rust/
* lang.opt: Fix translation mistakes 2023 in
GCC/Rust [PR108890]
(line 67): change the inconsistent tab to spaces
(line 75): wrap bare placeholder `integer`
(line 79): remove redundant text of `Choose which`
(line 96): remove redundant text of `Choose which`
(line 112): remove redundant `Flag to`
(line 124): correct the exclusive term `When to stop`
(line 124): correct typo of `copimlation`

Signed-off-by: Tieway59 

-- 
You are receiving this mail because:
You are on the CC list for the bug.