From: jjasmine
gcc/rust/ChangeLog:
* ast/rust-expr.h:
Add support for AST to HIR inline asm translation
* hir/rust-ast-lower-base.cc (ASTLoweringBase::visit): Likewise.
* hir/rust-ast-lower-base.h: Likewise.
* hir/rust-ast-lower-expr.cc (ASTLoweringExpr
e the precondition that used SSA defs fed to
vn_valueize are valid to use (including their associated ranges).
The following makes sure to replace those with new representatives
always, not only when the dependent expression translation changed it.
The fix was originally discovered by Michael
pl))
@@ -13162,28 +13408,36 @@ depset::hash::make_dependency (tree decl, entity_kind
ek)
dep->cluster = index - from->entity_lwm;
dep->section = from->remap;
dep->set_flag_bit ();
+
+ if (!from->is_header ())
+
On 12/18/24 9:17 AM, Nathaniel Shead wrote:
On Tue, Dec 17, 2024 at 03:58:38PM -0500, Jason Merrill wrote:
On 11/27/24 3:53 AM, Nathaniel Shead wrote:
Gentle ping for this series:
https://gcc.gnu.org/pipermail/gcc-patches/2024-October/665108.html
Most of the patches no longer applied cleanly t
On Tue, Dec 17, 2024 at 03:58:38PM -0500, Jason Merrill wrote:
> On 11/27/24 3:53 AM, Nathaniel Shead wrote:
> > Gentle ping for this series:
> > https://gcc.gnu.org/pipermail/gcc-patches/2024-October/665108.html
> >
> > Most of the patches no longer applied cleanly to trunk since the last
> > tim
On 11/27/24 3:53 AM, Nathaniel Shead wrote:
Gentle ping for this series:
https://gcc.gnu.org/pipermail/gcc-patches/2024-October/665108.html
Most of the patches no longer applied cleanly to trunk since the last
time I pinged this so I'm attaching newly rebased patches.
One slight adjustment I've
On Sat, 16 Nov 2024, Martin Uecker wrote:
> c: fix incorrect TBAA for tagged types across translation units [PR117490]
>
> Two different declarations of tagged types in the same translation unit
> are incompatible in C before C23 and without tag also in C23. Stil
. With this change, this issue now also affects tagless types.
I still hope this can be resolved in time for GCC 15.
Bootstrapped and regression tested on x86_64.
c: fix incorrect TBAA for tagged types across translation units [PR117490]
Two different declarations of tagged types in
cument -Wignored-exposures.
> +* doc/invoke.texi: Document -Wtemplate-names-tu-local.
>
> gcc/testsuite/ChangeLog:
>
> @@ Commit message
> * g++.dg/modules/internal-6.C: New test.
> * g++.dg/modu
+
- Wignored-qualifiers
- C C++ Var(warn_ignored_qualifiers) Warning EnabledBy(Wextra)
- Warn whenever type qualifiers are ignored.
+ Wterminate
+ C++ ObjC++ Warning Var(warn_terminate) Init(1)
+ Warn if a throw expression will always result in a call to terminate().
## gcc/
This patch series implements most of the changes made by P1815. It also
cleans up a few bugs found along the way that impacted tests I wrote.
The whole patch series was bootstrapped on x86_64-pc-linux-gnu and
aarch64-unknown-linux-gnu with no regressions.
Changes since v1:
- Merged in already a
This patch series implements most of the changes made by P1815. It also
cleans up a few bugs found along the way that impacted tests I wrote.
The whole patch series was bootstrapped on x86_64-pc-linux-gnu with no
regressions.
Nathaniel Shead (10):
libstdc++: Remove unnecessary 'static' from __
sertion if we then come across this header
as an #include and attempt to translate it into a module. We still need
to do this translation so that libcpp learns that this is a header unit,
but we shouldn't error just because we've already seen it as an import.
Instead this patch mere
On 8/22/24 7:49 AM, Nathaniel Shead wrote:
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk?
OK.
-- >8 --
Currently the handling of include translation is confusing to read,
using a tri-state integer without much clarity on what different states
mean. This patch cleans t
#include and attempt to translate it into a module. We still need
to do this translation so that libcpp learns that this is a header unit,
but we shouldn't error just because we've already seen it as an import.
Instead this patch merely checks and errors to handle the case of a
broken mapp
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk?
-- >8 --
Currently the handling of include translation is confusing to read,
using a tri-state integer without much clarity on what different states
mean. This patch cleans this up to use explicit enumerators indicating
The musttail error messages are reported to the user, so must be
translated.
gcc/ChangeLog:
PR83324
* calls.cc (initialize_argument_information): Mark messages
for translation.
(can_implement_as_sibling_call_p): Dito.
(expand_call): Dito.
---
gcc/calls.cc
On Sat, Jun 22, 2024 at 8:58 PM Andi Kleen wrote:
>
> The musttail error messages are reported to the user, so must be
> translated.
OK.
> gcc/ChangeLog:
>
> * calls.cc (initialize_argument_information): Mark messages
> for translation.
> (can_imp
The musttail error messages are reported to the user, so must be
translated.
gcc/ChangeLog:
* calls.cc (initialize_argument_information): Mark messages
for translation.
(can_implement_as_sibling_call_p): Dito.
(expand_call): Dito.
---
gcc/calls.cc | 56
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
Within a source file, #include is translated to import if a suitable header
unit is available, but this wasn't working with -include. This turned out
to be because we suppressed the translation before the beginning of the
m
gcc/testsuite/
* c-c++-common/initpri1.c: Split into...
* c-c++-common/initpri1_part_c1.c: ... this, and...
* c-c++-common/initpri1_part_c2.c: ... this, and...
* c-c++-common/initpri1_part_c3.c: ... this, and...
* c-c++-common/initpri1_part_cd4.c: ...
ertions(+)
diff --git a/.gitattributes b/.gitattributes
index e75bfc595bf..1e116987c98 100644
--- a/.gitattributes
+++ b/.gitattributes
@@ -8,3 +8,6 @@ ChangeLog
whitespace=indent-with-non-tab,space-before-tab,trailing-space
# Use together with git config diff.md.xfuncname '^\(define.*$'
> --- a/.gitattributes
> +++ b/.gitattributes
> @@ -8,3 +8,6 @@ ChangeLog
> whitespace=indent-with-non-tab,space-before-tab,trailing-space
> # Use together with git config diff.md.xfuncname '^\(define.*$'
> # which is run by contrib/gcc-git-customization.sh too.
> *.md diff=md
> +
> +# Disable lf -> crlf translation on windows.
> +* -crlf
> --
> 2.39.2
>
,3 +8,6 @@ ChangeLog
whitespace=indent-with-non-tab,space-before-tab,trailing-space
# Use together with git config diff.md.xfuncname '^\(define.*$'
# which is run by contrib/gcc-git-customization.sh too.
*.md diff=md
+
+# Disable lf -> crlf translation on windows.
+* -crlf
--
2.39.2
PRE implicitely keeps virtual operands at the blocks incoming version
but the explicit updating point during PHI translation fails to trigger
when there are no PHIs at all in a block. Later lazy updating then
fails because of a too lose block check. A similar issues plagues
reference
This amends an error message to correct punctuation and a little
better wording.
bootstrapped on x86_64-darwin18, pushed to master,
thanks, Iain
Signed-off-by: Iain Sandoe
PR translation/104552
gcc/ChangeLog:
* config/host-darwin.cc (darwin_gt_pch_get_address): Amend
> -Original Message-
> From: Gcc-patches bounces+kyrylo.tkachov=arm@gcc.gnu.org> On Behalf Of Martin Liška
> Sent: Monday, March 7, 2022 10:22 AM
> To: Christophe Lyon ; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH][ARM] translation: reuse string and use switch f
On 3/7/22 11:18, Christophe Lyon via Gcc-patches wrote:
Hi!
On 3/7/22 11:09, Martin Liška wrote:
Hi.
The patch simplifies translation strings.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
This is an arm-only patch, it's not clear if you built a cross-compile
Hi!
On 3/7/22 11:09, Martin Liška wrote:
Hi.
The patch simplifies translation strings.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
This is an arm-only patch, it's not clear if you built a cross-compiler
for arm, and that these regression tests passed?
Rea
:56:43 +0100
Subject: [PATCH] translation: reuse string and use switch for codes
gcc/ChangeLog:
* config/arm/arm-builtins.cc (arm_expand_builtin): Reuse error
message.
---
gcc/config/arm/arm-builtins.cc | 127 -
1 file changed, 77 insertions(+), 50 deletions
+0100
Subject: [PATCH] translation: reuse string and use switch for codes
gcc/ChangeLog:
* config/arm/arm-builtins.cc (arm_expand_builtin): Reuse error
message.
---
gcc/config/arm/arm-builtins.cc | 125 -
1 file changed, 75 insertions(+), 50 deletions(-)
diff --git
On Mon, Mar 07, 2022 at 11:09:26AM +0100, Martin Liška wrote:
> gcc/ChangeLog:
>
> * config/arm/arm-builtins.cc (arm_expand_builtin): Reuse error
> message.
Will defer review to ARM maintainers, just wanted to mention some of the
lines are way too long (before or after).
> --- a/gcc/
Hi.
The patch simplifies translation strings.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
gcc/ChangeLog:
* config/arm/arm-builtins.cc (arm_expand_builtin): Reuse error
message.
---
gcc/config/arm/arm
The logic in libcpp/Makefile.in listing diagnostic functions in a call
to xgettext was missing cpp_warning_at, cpp_pedwarning_at and
cpp_error_at, so resulting in some messages not being extracted for
translation; add those functions to those for which messages are
extracted.
Tested with "
On Sun, 21 Nov 2021 19:59:35 +0100
Harald Anlauf wrote:
> Let's have a look at the tree-dump of the existing testcase:
>
> integer(kind=4) runtime_poppar (integer(kind=16) & restrict i)
> {
>integer(kind=4) res;
>
>{
> uint128_t D.4221;
>
> D.4221 = (uint128_t) *i;
> res
Let's have a look at the tree-dump of the existing testcase:
integer(kind=4) runtime_poppar (integer(kind=16) & restrict i)
{
integer(kind=4) res;
{
uint128_t D.4221;
D.4221 = (uint128_t) *i;
res = __builtin_parityll ((unsigned long) D.4221 ^ (unsigned long)
(D.4221 >> 64));
}
Roger pinged this on gcc-patches some time ago fwiw.
[The commit-hooks will likely fix or ignore s/bext/next/ in his
mail-addr]
On Sun, 14 Jun 2020 23:39:32 +0100
"Roger Sayle" wrote:
>
>
> The following patch to gfortran's trans-instrinsic.c tweaks the generic that
> is produced
>
> for po
This gets rid of the DECL_STUBBED_P macro and adjusts Call_to_gnu.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* gcc-interface/ada-tree.h (DECL_STUBBED_P): Delete.
* gcc-interface/decl.c (gnat_to_gnu_entity): Do not set it.
* gcc-interface/trans.c (Call_to_
When translating literals to big reals, the compiler would forget about
the minus sign and turn a negative number into a positive one.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_res.adb (Resolve): Insert minus sign if needed.diff --git a/gcc/ada/sem_res.adb b/gcc/ad
Hi
I modified the diagnostic message to avoid a build-time warning
omitting a colon intentionally; since that has produced a translation
comment, this adds the colon back.
tested with a build of host-darwin (produces no build-time diagnostic).
pushed to master,
thanks
Iain
Add a '
We make sure files end in \n by placing one at the limit of the buffer
(just past the end of what is read). We need to do the same for buffers
generated via include-translation. Fortunately they have space.
libcpp/
* files.c (_cpp_stack_file): Make buffers end in unread \n
Hi,
I hope you are doing well!
This is Suzy, an account manager from an ISO 9001:2008 Translation Company.
I happened to browse your website today, so I thought that maybe you’d like to
work with native Asian linguists for your projects, and that's exactly why I'm
reaching
This adds preprocessor support for header units. Every #include
directive needs to go through the include-translation hook to determine
if it is to be treated as 'import $file;'. This is that code. when
include translation occurs, the hook creates a buffer containing the
transl
n-ids provide a closer
approximation of a topological sort since those are assigned
during AVAIL_OUT computation which is done in a dominator walk.
Now - phi-translation is not even depending on topological sorting
but it essentially does a DFS walk, phi-translating expressions
it depends on and relyi
This changes the phi translation cache to be per edge which
pushes it off the profiling radar. For larger testcases the
combined hashtable causes a load of cache misses and making it
per edge allows to shrink the entry further.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
2020
the expression. */
- basic_block pred;
+ /* The expression ID. */
+ unsigned e;
- /* The value that resulted from the translation. */
- pre_expr v;
+ /* The predecessor block index along which we translated the expression. */
+ int pred;
- /* The hashcode for the expression, pred pair.
Mark,
A full bootstrap is successful with the translation markers restored
and declaring hint as "const char *".
const char *hint = _(" [see %<-fno-allow-invalid-boz%>]");
I assume that the translation system works correctly for that style.
Do you want to apply the
20:07, David Edelsohn wrote:
> > >>>> This patch breaks bootstrap.
> > >>> Apologies. I didn't see this when I built the compiler the with
> > >>> bootstrap on x86_64. I'll endevour to get it fixed as soon as possible.
> > > Mark,
> > &g
ndevour to get it fixed as soon as possible.
> > Mark,
> >
> > Your change did nothing because I previously had removed the
> > translation markers to restore bootstrap. You were not sufficiently
> > observant to check the ChangeLog or notice that the line alread
David Edelsohn wrote:
This patch breaks bootstrap.
Apologies. I didn't see this when I built the compiler the with
bootstrap on x86_64. I'll endevour to get it fixed as soon as
possible.
Mark,
Your change did nothing because I previously had removed the
translation markers to restore
strap.
Apologies. I didn't see this when I built the compiler the with
bootstrap on x86_64. I'll endevour to get it fixed as soon as possible.
Mark,
Your change did nothing because I previously had removed the
translation markers to restore bootstrap. You were not sufficiently
observa
>
> > Apologies. I didn't see this when I built the compiler the with
> > bootstrap on x86_64. I'll endevour to get it fixed as soon as possible.
Mark,
Your change did nothing because I previously had removed the
translation markers to restore bootstrap. You were not
I already had removed your change. I hope that you did not re-break bootstrap.
You should be re-producing the breakage and then confirming the fix,
not randomly applying patches and asking others if you didn't break it
again. That is not appropriate for GCC development.
Thanks David
On Thu, Ju
I've committed the change from array to pointer. Does this fix your builds?
On 02/07/2020 08:18, Mark Eggleston wrote:
On 01/07/2020 20:07, David Edelsohn wrote:
This patch breaks bootstrap.
Apologies. I didn't see this when I built the compiler the with
bootstrap on x86_64. I'll endevour to
On 01/07/2020 20:07, David Edelsohn wrote:
This patch breaks bootstrap.
Apologies. I didn't see this when I built the compiler the with
bootstrap on x86_64. I'll endevour to get it fixed as soon as possible.
regards,
Mark
It is not portable to use _( ... ) to initialize an array.
In file
This patch breaks bootstrap.
It is not portable to use _( ... ) to initialize an array.
In file included from /nasfarm/edelsohn/src/src/gcc/fortran/gfortran.h:52,
from /nasfarm/edelsohn/src/src/gcc/fortran/check.c:32:
/nasfarm/edelsohn/src/src/gcc/fortran/check.c: In function 'bo
On 6/30/20 6:59 AM, Mark Eggleston wrote:
ping!
On 25/06/2020 07:28, Mark Eggleston wrote:
Patch to fix PR52279. Marked strings that are indirectly used in
error and warning messages so that they are marked for translation.
OK to commit?
Commit message:
Fortran : Fortran transla
Hi Mark,
that one is OK for master. Thanks!
Regards
Thomas
ping!
On 25/06/2020 07:28, Mark Eggleston wrote:
Patch to fix PR52279. Marked strings that are indirectly used in
error and warning messages so that they are marked for translation.
OK to commit?
Commit message:
Fortran : Fortran translation issues PR52279
Mark strings for translation by
Patch to fix PR52279. Marked strings that are indirectly used in error
and warning messages so that they are marked for translation.
OK to commit?
Commit message:
Fortran : Fortran translation issues PR52279
Mark strings for translation by enclosing in G_() and _().
2020-06-24 Mark
The following patch to gfortran's trans-instrinsic.c tweaks the generic that
is produced
for popcnt on integer(kind=16). Currently, the double word popcnt is
implemented as
parityll(hipart(x))^parityll(lopart(x)), but with this patch this is now
translated as
parityll(hipart(x)^lopart(x)).
This updates the options descriptions after feedback from a translator.
tested on x86_64-darwin16,
applied to master,
thanks
Iain
gcc/ChangeLog:
2020-03-21 Iain Sandoe
PR target/93694
* gcc/config/darwin.opt: Amend options descriptions.
diff --git a/gcc/ChangeLog
On Tue, 18 Feb 2020, Jakub Jelinek wrote:
> Hi!
>
> The first two hunks make sure we actually translate what has been marked
> for translation, i.e. the cl_options[...].help strings, rather than those
> strings ammended in various ways, like:
> _("%s Same as %s."
Hi!
The first two hunks make sure we actually translate what has been marked
for translation, i.e. the cl_options[...].help strings, rather than those
strings ammended in various ways, like:
_("%s Same as %s."), help, ...
or
"%s %s", help, _(use_diagnosed_msg)
The exgettex
Not a regression, but only affects a diagnostic on the H8 port.
As pointed out in the BZ, we should not be emitting an exclamation
point in the diagnostic and the capitalization was incorrect. Fixed by
the attached patch which I've committed to the trunk.
Jeff
commit dfa075d00d396f554b4aca183c3c
> > > On Fri, Dec 13, 2019 at 11:26 AM bin.cheng
> > > > wrote:
> > > > > Hi,
> > > > >
> > > > > As reported in PR92926, constant ctor is shared translation unit wide
> > > > because of constexpr_call_table,
> > &g
> > > Hi,
> > > >
> > > > As reported in PR92926, constant ctor is shared translation unit wide
> > > because of constexpr_call_table,
> > > > however, during gimplify, the shared ctor could be modified. This
> > > patch fixes the
On 1/9/20 4:37 PM, Jakub Jelinek wrote:
On Thu, Jan 09, 2020 at 04:27:09PM -0500, Jason Merrill wrote:
Isn't the right spot to fix this somewhere in cp_gimplify_expr?
I mean, the way gimplification works, we unshare_body first and then
gimplify, which is destructive for the GENERIC it is gimplif
On Thu, Jan 09, 2020 at 04:27:09PM -0500, Jason Merrill wrote:
> > Isn't the right spot to fix this somewhere in cp_gimplify_expr?
> > I mean, the way gimplification works, we unshare_body first and then
> > gimplify, which is destructive for the GENERIC it is gimplifying. The
> > reason why this
On 1/9/20 3:59 AM, Jakub Jelinek wrote:
On Thu, Jan 09, 2020 at 02:20:23PM +0800, Bin.Cheng wrote:
On December 20, 2019 2:13:47 AM GMT+01:00, "Bin.Cheng"
wrote:
On Fri, Dec 13, 2019 at 11:26 AM bin.cheng
wrote:
Hi,
As reported in PR92926, constant ctor is shared translation
On Thu, Jan 09, 2020 at 02:20:23PM +0800, Bin.Cheng wrote:
> > On December 20, 2019 2:13:47 AM GMT+01:00, "Bin.Cheng"
> > wrote:
> > >On Fri, Dec 13, 2019 at 11:26 AM bin.cheng
> > > wrote:
> > >>
> > >> Hi,
> > >>
On Fri, Dec 20, 2019 at 3:10 PM Richard Biener
wrote:
>
> On December 20, 2019 2:13:47 AM GMT+01:00, "Bin.Cheng"
> wrote:
> >On Fri, Dec 13, 2019 at 11:26 AM bin.cheng
> > wrote:
> >>
> >> Hi,
> >>
> >> As reported in P
On December 20, 2019 2:13:47 AM GMT+01:00, "Bin.Cheng"
wrote:
>On Fri, Dec 13, 2019 at 11:26 AM bin.cheng
> wrote:
>>
>> Hi,
>>
>> As reported in PR92926, constant ctor is shared translation unit wide
>because of constexpr_call_table,
>> h
On Fri, Dec 13, 2019 at 11:26 AM bin.cheng wrote:
>
> Hi,
>
> As reported in PR92926, constant ctor is shared translation unit wide because
> of constexpr_call_table,
> however, during gimplify, the shared ctor could be modified. This patch
> fixes the issue by
This patch was previously approved here, but I have not committed it yet
(without the other patches in this series):
https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01156.html
Included for completeness. I will commit this alongside other patches
if they are approved (or it could probably go in by
Hi,
As reported in PR92926, constant ctor is shared translation unit wide because
of constexpr_call_table,
however, during gimplify, the shared ctor could be modified. This patch fixes
the issue by unsharing
it before modification in gimplify. A test is reduced from cppcoro library and
added
Hello Ma’am/Sir,
I represent a company which has *1**7**+* years of experience in
providing *accurate
Translation, Interpretation, App/Web Localization, and Content Moderation
Services within fastest TAT.*
Our team has expertise in all types of languages including national and
international
Hello Ma’am/Sir,
I represent a company which has *1**7**+* years of experience in
providing *accurate
Translation, Interpretation, App/Web Localization, and Content Moderation
Services within fastest TAT.*
Our team has expertise in all types of languages including national and
international
Hi!
On 2019-10-06T15:32:35-0700, Julian Brown wrote:
> This patch uses gomp_map_val for OpenACC host-to-device address
> translation instead of open-coding the device address calculation.
(As has been discussed before.)
(And then, also see <https://gcc.gnu.org/PR90596> "
This patch uses gomp_map_val for OpenACC host-to-device address
translation instead of open-coding the device address calculation.
OK for trunk?
Thanks,
Julian
ChangeLog
libgomp/
* libgomp.h (gomp_map_val): Add prototype.
* oacc-parallel.c (GOACC_parallel_keyed): Use
> From: Richard Sandiford
> Date: Tue, 1 Oct 2019 09:51:51 +0200
> Hans-Peter Nilsson writes:
> > My autotester for cris-elf complains about a build-breaking
> > commit in the revision range (working:breaking) 276299:276359
> Fixed as below. I also belatedly see a new definition of
> HARD_REGN
Hans-Peter Nilsson writes:
>> From: Richard Sandiford
>> Date: Wed, 11 Sep 2019 21:02:26 +0200
>
>> This series of patches introduces some classes and helpers for handling
>> multiple ABIs in the same translation unit. At the moment "ABI" maans
>>
> From: Richard Sandiford
> Date: Wed, 11 Sep 2019 21:02:26 +0200
> This series of patches introduces some classes and helpers for handling
> multiple ABIs in the same translation unit. At the moment "ABI" maans
> specifically the choice of call-clobbered registers
Dimitar Dimitrov writes:
> On Wed, 11 Sep 2019, 22:02:26 EEST Richard Sandiford wrote:
>> The reason for the PRU differences is that the port defines
>> targetm.hard_regno_call_part_clobbered, but uses it to test whether
>> a multi-register value contains a mixture of fully-clobbered and
>> fully-
On Wed, 11 Sep 2019, 22:02:26 EEST Richard Sandiford wrote:
> The reason for the PRU differences is that the port defines
> targetm.hard_regno_call_part_clobbered, but uses it to test whether
> a multi-register value contains a mixture of fully-clobbered and
> fully-preserved registers. AFAICT the
On Wednesday, September 11, 2019, Richard Sandiford <
richard.sandif...@arm.com> wrote:.
>
>
> Sorry for the long write-up.
>
> Richard
>
*thanks* for the long write-up!
Ciao!
Steven
This series of patches introduces some classes and helpers for handling
multiple ABIs in the same translation unit. At the moment "ABI" maans
specifically the choice of call-clobbered registers, but I'm hoping the
structures could be used for other ABI properties in future.
The ma
On 4/29/19 5:06 AM, Martin Liška wrote:
> Hi.
>
> Simple patch to address a missing translation of a string.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
>
> gcc/ChangeLog:
>
> 2
Hi.
Simple patch to address a missing translation of a string.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
gcc/ChangeLog:
2019-04-29 Martin Liska
PR translation/90274
* opts.c (print_filtered_help): Wrap
On 4/19/19 3:38 AM, Jakub Jelinek wrote:
On Fri, Apr 19, 2019 at 11:28:41AM +0200, Christophe Lyon wrote:
--- a/contrib/check-internal-format-escaping.py
+++ b/contrib/check-internal-format-escaping.py
@@ -58,6 +58,10 @@ for i, l in enumerate(lines):
print('%s: %s' % (o
On Fri, 19 Apr 2019 at 11:57, Richard Sandiford
wrote:
>
> Christophe Lyon writes:
> > On Fri, 19 Apr 2019 at 11:23, Richard Sandiford
> > wrote:
> >>
> >> Christophe Lyon writes:
> >> > On Thu, 18 Apr 2019 at 18:25, Richard Sandiford
> >> > wrote:
> >> >>
> >> >> Christophe Lyon writes:
> >>
Christophe Lyon writes:
> On Fri, 19 Apr 2019 at 11:23, Richard Sandiford
> wrote:
>>
>> Christophe Lyon writes:
>> > On Thu, 18 Apr 2019 at 18:25, Richard Sandiford
>> > wrote:
>> >>
>> >> Christophe Lyon writes:
>> >> > Hi,
>> >> >
>> >> > This patch adds the missing space before '%<' in
>>
On Fri, Apr 19, 2019 at 11:28:41AM +0200, Christophe Lyon wrote:
> > >> > --- a/contrib/check-internal-format-escaping.py
> > >> > +++ b/contrib/check-internal-format-escaping.py
> > >> > @@ -58,6 +58,10 @@ for i, l in enumerate(lines):
> > >> > print('%s: %s' % (origin, te
On Fri, 19 Apr 2019 at 11:23, Richard Sandiford
wrote:
>
> Christophe Lyon writes:
> > On Thu, 18 Apr 2019 at 18:25, Richard Sandiford
> > wrote:
> >>
> >> Christophe Lyon writes:
> >> > Hi,
> >> >
> >> > This patch adds the missing space before '%<' in
> >> > config/aarch64/aarch64.c and gcc/c
Christophe Lyon writes:
> On Thu, 18 Apr 2019 at 18:25, Richard Sandiford
> wrote:
>>
>> Christophe Lyon writes:
>> > Hi,
>> >
>> > This patch adds the missing space before '%<' in
>> > config/aarch64/aarch64.c and gcc/cp/call.c. It also updates the
>> > check-internal-format-escaping.py checker
On Thu, 18 Apr 2019 at 18:25, Richard Sandiford
wrote:
>
> Christophe Lyon writes:
> > Hi,
> >
> > This patch adds the missing space before '%<' in
> > config/aarch64/aarch64.c and gcc/cp/call.c. It also updates the
> > check-internal-format-escaping.py checker to warn about such cases.
> >
> > O
Christophe Lyon writes:
> Hi,
>
> This patch adds the missing space before '%<' in
> config/aarch64/aarch64.c and gcc/cp/call.c. It also updates the
> check-internal-format-escaping.py checker to warn about such cases.
>
> OK?
>
> Christophe
>
> diff --git a/contrib/check-internal-format-escaping.
%T)%> ", msg, fn,
candidate->convs[0]->type,
candidate->convs[1]->type);
else
- inform (cloc, "%s%<%D(%T)%> ", msg, fn,
+ inform (cloc, "%s %<%D(%T)%> ", msg, fn,
candidate->convs[0]-
tml_node/Plural-forms.html#Plural-forms
> for more details.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, plus generated
> gcc.pot and eyeballed the changes. Ok for trunk?
OK.
Richard.
> 2019-04-18 Jakub Jelinek
>
> PR translation/79183
> * gim
ed on x86_64-linux and i686-linux, plus generated
gcc.pot and eyeballed the changes. Ok for trunk?
2019-04-18 Jakub Jelinek
PR translation/79183
* gimple-ssa-sprintf.c (format_directive): Use inform_n instead of
inform where appropriate.
--- gcc/gimple-ssa-sprintf.c.jj
1 - 100 of 238 matches
Mail list logo
