Hi,
There are currently two situations where this assert triggers:
...
libgomp/plugin/plugin-nvptx.c: map_fini: Assertion `!s->map->active' failed.
...
First, in abort-1.c, a parallel region triggering an abort:
...
int
main (void)
{
#pragma acc parallel
abort ();
return 0;
}
...
The
On Tue, Jan 22, 2019 at 9:59 PM Thomas Koenig wrote:
>
> Hello world,
>
> the attached patch moves the packing / unpacking of arrays to the front
> end when optimizing, but not for size.
>
> Rationale: internal_pack and internal_unpack are opaque to the compiler.
> This can lead to a lot of
Hi,
The map field of a struct ptx_stream is a FIFO. The FIFO is implemented as a
single linked list, with pop-from-the-front semantics.
The function map_pop pops an element, either by:
- deallocating the element, if there is more than one element
- or marking the element inactive, if there's
On Tue, 22 Jan 2019, Jakub Jelinek wrote:
> Hi!
>
> SCEV can analyze not just integral/pointer IVs, but (scalar) float ones as
> well. Calling build_int_cst on such types results in ICE, build_zero_cst
> works. Though the loop invariant PHI IVs, if we represent them as using
> +0.0 step,
Hi,
Consider test-case:
...
int
main (void)
{
#pragma acc parallel async
;
#pragma acc parallel async
;
#pragma acc wait
return 0;
}
...
This fails with:
...
libgomp: cuMemAlloc error: invalid argument
Segmentation fault (core dumped)
...
The cuMemAlloc error is due to the fact that
On 1/22/19 10:50 AM, Gerald Pfeifer wrote:
> I've been seeing the following in my testsuite runs which I didn't
> get a month or so ago. Are these due to your changes, Jakub, or
> some changes around libbacktrace?
I can confirm that and I've just created a PR for it:
Hi Thomas,
With your patch I see
FAIL: gfortran.dg/internal_pack_4.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
with -m32.
gfc /opt/gcc/work/gcc/testsuite/gfortran.dg/internal_pack_4.f90 -O3
-funroll-loops -ftracer -m32
is enough to
On Wed, 23 Jan 2019, Alexander Monakov wrote:
> That said, I'm really concerned that on this testcase we should not be moving
> the tablejump *at all*: we are moving it up past a 'use ax' insn (the use is
> for the function's return value). So after the move the use is in an
> unreachable
>
On 1/23/19 9:26 AM, Ramana Radhakrishnan wrote:
On Wed, Jan 23, 2019 at 1:54 PM Jason Merrill wrote:
Since in r265788 I made cxx_eval_outermost_constant_expr more insistent that
the returned value have the right type, it became more important that
initialized_type be correct. These two PRs
On 1/23/19 11:05 AM, Marek Polacek wrote:
Since C++20 P0634R3 we sometimes treat certain qualified-ids as types, so that
the user doesn't have to type 'typename'. But this was broken for this case:
template T::type N::v(T::value);
which, if T::value is a type, is a function template
On Wed, 23 Jan 2019 at 16:28, Jonathan Wakely wrote:
>
> On 09/01/19 13:53 +0100, Christophe Lyon wrote:
> >On Wed, 9 Jan 2019 at 11:11, Jonathan Wakely wrote:
> >>
> >> On 09/01/19 10:09 +, Jonathan Wakely wrote:
> >> >On 08/01/19 11:13 +0100, Christophe Lyon wrote:
> >> >>On Mon, 7 Jan
Running:
$ valgrind ./xgcc -B. -c test.c -march=native
on aarch64 shows a use-after-free in host_detect_local_cpu due
to the std::string result of aarch64_get_extension_string_for_isa_flags
only living until immediately after a c_str call.
This leads to corrupt "-march=" values being passed to
On 23/01/2019 17:12, David Malcolm wrote:
> Running:
> $ valgrind ./xgcc -B. -c test.c -march=native
> on aarch64 shows a use-after-free in host_detect_local_cpu due
> to the std::string result of aarch64_get_extension_string_for_isa_flags
> only living until immediately after a c_str call.
>
>
On Thu, Jan 10, 2019 at 04:57:47PM +, Kyrill Tkachov wrote:
> --- a/gcc/config/aarch64/driver-aarch64.c
> +++ b/gcc/config/aarch64/driver-aarch64.c
> @@ -253,6 +253,12 @@ host_detect_local_cpu (int argc, const char **argv)
> char *p = NULL;
> char *feat_string
>
The test gcc.dg/torture/pr84682-2.c has been failing for some time on
aarch64. Bin Cheng submitted a patch for this some time ago, the
original patch was:
https://gcc.gnu.org/ml/gcc-patches/2018-03/msg00784.html
But Richard Sandiford thought it should be fixed in recog.c instead of
just in
Steve Ellcey writes:
> The test gcc.dg/torture/pr84682-2.c has been failing for some time on
> aarch64. Bin Cheng submitted a patch for this some time ago, the
> original patch was:
>
> https://gcc.gnu.org/ml/gcc-patches/2018-03/msg00784.html
>
> But Richard Sandiford thought it should be fixed
On 09/01/19 13:53 +0100, Christophe Lyon wrote:
On Wed, 9 Jan 2019 at 11:11, Jonathan Wakely wrote:
On 09/01/19 10:09 +, Jonathan Wakely wrote:
>On 08/01/19 11:13 +0100, Christophe Lyon wrote:
>>On Mon, 7 Jan 2019 at 15:14, Christophe Lyon
wrote:
>>>
>>>On Mon, 7 Jan 2019 at 13:39,
Since C++20 P0634R3 we sometimes treat certain qualified-ids as types, so that
the user doesn't have to type 'typename'. But this was broken for this case:
template T::type N::v(T::value);
which, if T::value is a type, is a function template declaration. But if
T::value is a value, it's a
On Tue, Jan 22, 2019 at 02:10:38PM +, Bernd Edlinger wrote:
> --- gcc/c-family/c-warn.c (revision 268119)
> +++ gcc/c-family/c-warn.c (working copy)
> @@ -2796,6 +2796,10 @@ check_address_or_pointer_of_packed_membe
> if (context)
> break;
> }
> + if
On Wed, 2019-01-23 at 12:50 +, Tamar Christina wrote:
> Hi Steve,
>
> >
> > Hi Steve,
> >
> > No we are using aarch64_be-*-* but this is the only one that popped
> > up as a
> > failure which is why I didn't change the others.
> > But now I'm wondering why... I'll check the log file
Hi!
On Tue, Dec 04, 2018 at 10:12:51AM -0600, Peter Bergner wrote:
> We talked about replacing rs6000'c regno_or_subregno() with the generic
> reg_or_subregno() function from jump.c. I agree the geberic version is
> better because it has an assert that ensures we have a REG. There were
> also a
Attached patch adds SSE alternatives to sse2_cvtpi2pd, sse2_cvtpd2pi
and sse2_cvttpd2pi to avoid MMX registers when e.g. _mm_cvtepi32_pd
intrinsics is used. Without the patch, the testcase compiles to (-O2
-mavx):
_Z7prepareii:
vmovd %edi, %xmm1
vpinsrd $1, %esi, %xmm1, %xmm0
I ran libstdc++ tests on nios2-elf target. I observed several new tests
failing with
error: 'mutex' in namespace 'std' does not name a type
The definition of class mutex in include/bits/std_mutex.h is guarded
with "#ifdef _GLIBCXX_HAS_GTHREADS" so I assume these tests are not
supposed to
On Wed, Jan 23, 2019 at 11:22 AM Uros Bizjak wrote:
>
> Attached patch adds SSE alternatives to sse2_cvtpi2pd, sse2_cvtpd2pi
> and sse2_cvttpd2pi to avoid MMX registers when e.g. _mm_cvtepi32_pd
> intrinsics is used. Without the patch, the testcase compiles to (-O2
> -mavx):
>
> _Z7prepareii:
>
On Wed, Jan 23, 2019 at 04:52:24PM +0300, Alexander Monakov wrote:
> On Wed, 23 Jan 2019, Andrey Belevantsev wrote:
> > For that, I'm not sure. Your patch will leave the tablejump unscheduled at
> > all, i.e. any fields like INSN_TICK would be unfilled and thus the later
> > passes like bundling
The attached patch allows MPICH 3.2 to build correctly and to test successfully.
Two problems were addressed:
(i) The original implementation of ISO_Fortran_binding did not take
account of the possibility that assumed rank/assumed type arrays could
be passed as dummy arguments. This necessitated
On Wed, Jan 23, 2019 at 09:00:36AM -0500, Jason Merrill wrote:
> I was talking about digest_init, not reshape_init. digest_init calls
> convert_for_initialization.
/facepalm
So yes, digest_init calls convert_for_initialization which will end up
calling perform_implicit_conversion_flags which
Hi Martin,
On Wed, Jan 23, 2019 at 10:29:40AM +0100, Martin Liška wrote:
> diff --git a/gcc/cfgrtl.c b/gcc/cfgrtl.c
> index 172bdf585d0..5dd316efb63 100644
> --- a/gcc/cfgrtl.c
> +++ b/gcc/cfgrtl.c
> @@ -4396,6 +4396,25 @@ cfg_layout_redirect_edge_and_branch (edge e,
> basic_block dest)
>
On 1/23/19 4:22 PM, Jakub Jelinek wrote:
> On Tue, Jan 22, 2019 at 02:10:38PM +, Bernd Edlinger wrote:
>> --- gcc/c-family/c-warn.c(revision 268119)
>> +++ gcc/c-family/c-warn.c(working copy)
>> @@ -2796,6 +2796,10 @@ check_address_or_pointer_of_packed_membe
>>if (context)
>>
Hi Dominique,
FAIL: gfortran.dg/internal_pack_4.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
with -m32.
gfc /opt/gcc/work/gcc/testsuite/gfortran.dg/internal_pack_4.f90 -O3
-funroll-loops -ftracer -m32
is enough to trigger the
On Wed, Jan 23, 2019 at 8:52 PM H.J. Lu wrote:
>
> On Wed, Jan 23, 2019 at 11:22 AM Uros Bizjak wrote:
> >
> > Attached patch adds SSE alternatives to sse2_cvtpi2pd, sse2_cvtpd2pi
> > and sse2_cvttpd2pi to avoid MMX registers when e.g. _mm_cvtepi32_pd
> > intrinsics is used. Without the patch,
On Wed, Jan 23, 2019 at 12:50 PM Joseph Myers wrote:
>
> On Wed, 23 Jan 2019, H.J. Lu wrote:
>
> > + fesetround (FE_DOWNWARD);
> > + float fs = s128;
> > + if (fs != -0x1p+127)
> > +abort ();
> > + double ds = s128;
> > + if (ds != -0x1p+127)
> > +abort ();
>
> This definitely needs
Hi,
for the record, the attached version of the patch regtests cleanly and
also passes the test that Dominique pointed out.
I will defer this until stage 1 reopens.
Regards
Thomas
Index: fortran/expr.c
===
---
On Wed, Jan 23, 2019 at 12:57 PM Marek Polacek wrote:
>
> On Wed, Jan 23, 2019 at 09:00:36AM -0500, Jason Merrill wrote:
> > I was talking about digest_init, not reshape_init. digest_init calls
> > convert_for_initialization.
>
> /facepalm
>
> So yes, digest_init calls convert_for_initialization
On Wed, 23 Jan 2019, H.J. Lu wrote:
> + fesetround (FE_DOWNWARD);
> + float fs = s128;
> + if (fs != -0x1p+127)
> +abort ();
> + double ds = s128;
> + if (ds != -0x1p+127)
> +abort ();
This definitely needs #ifdef FE_DOWNWARD; even just limited to glibc
configurations, there are
On Wed, Jan 23, 2019 at 12:27 PM Uros Bizjak wrote:
>
> On Wed, Jan 23, 2019 at 8:52 PM H.J. Lu wrote:
> >
> > On Wed, Jan 23, 2019 at 11:22 AM Uros Bizjak wrote:
> > >
> > > Attached patch adds SSE alternatives to sse2_cvtpi2pd, sse2_cvtpd2pi
> > > and sse2_cvttpd2pi to avoid MMX registers
On Wed, 2019-01-23 at 16:54 +, Richard Sandiford wrote:
>
> IMO we shouldn't remove the assert. See:
>
> https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01969.html
>
> and the thread leading up to it.
>
> Thanks,
> Richard
OK, I hadn't seen that thread. I didn't see any patch submitted
Steve Ellcey writes:
> On Wed, 2019-01-23 at 16:54 +, Richard Sandiford wrote:
>>
>> IMO we shouldn't remove the assert. See:
>>
>> https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01969.html
>>
>> and the thread leading up to it.
>>
>> Thanks,
>> Richard
>
> OK, I hadn't seen that
On Wed, Jan 23, 2019 at 07:43:48PM +, Paul Richard Thomas wrote:
>
> Bootstrapped and regtested on FC28/x86_64 - OK for trunk?
>
Yes with minor fixes.
> Index: gcc/fortran/trans-array.c
> ===
> *** gcc/fortran/trans-array.c
On Tue, 2019-01-22 at 13:18 +0100, Richard Biener wrote:
>
> Yeah, I would even suggest to use a target hook multilib_ABI_active_p
> (const char *)
> for this ... (where the hook should diagnose unknown multilib specifiers).
>
> Richard.
I wonder if we even need to pass a string to the target
On 23/01/2019 13:19, Jakub Jelinek wrote:
On Wed, Jan 23, 2019 at 11:30:29AM +, Jonny Grant wrote:
Not a member of this list, please include my email address in any replies.
2019-01-23 Jonny Grant
PR 89010
PR sanitizer/89010
is what should be used.
*
Hi!
We forgot to bump BASE-VER when we've entered stage4, doing it now:
2019-01-23 Jakub Jelinek
* BASE-VER: Bump to 9.0.1.
--- gcc/BASE-VER(revision 268183)
+++ gcc/BASE-VER(revision 268184)
@@ -1 +1 @@
-9.0.0
+9.0.1
Jakub
On Wed, 23 Jan 2019, Andrey Belevantsev wrote:
> For that, I'm not sure. Your patch will leave the tablejump unscheduled at
> all, i.e. any fields like INSN_TICK would be unfilled and thus the later
> passes like bundling on ia64 will not work. Maybe we can just stop
> tablejumps from moving
Since in r265788 I made cxx_eval_outermost_constant_expr more insistent that
the returned value have the right type, it became more important that
initialized_type be correct. These two PRs were cases of it giving the wrong
answer. On ARM, a constructor returns a pointer to the object, but
On 1/22/19 5:25 PM, Jakub Jelinek wrote:
Hi!
This patch adjusts genericize_cp_loop similarly to the
PR88984 change in genericize_switch_stmt, so that the following testcase now
behaves the same in both C and C++, plus adds the testcase and
documentation.
Bootstrapped/regtested on
On 1/22/19 5:25 PM, Jakub Jelinek wrote:
Hi!
The following testcase ICEs, because we assert that if during parsing we
haven't found any break; stmts in SWITCH_STMT_BODY, the switch statement
break label will not be used. It is used in this case though, because
while during parsing we expect
On 1/22/19 4:10 PM, Marek Polacek wrote:
On Mon, Jan 21, 2019 at 03:14:53PM -0500, Jason Merrill wrote:
On 1/18/19 9:12 AM, Marek Polacek wrote:
On Thu, Jan 17, 2019 at 04:17:29PM -0500, Jason Merrill wrote:
On 1/17/19 2:09 PM, Marek Polacek wrote:
This patch ought to fix the rest of 78244,
$subject - on trunk the PR is hidden because those do not appear
for other reasons. Still stray * 0 are prone to causing failures
thus the following.
On the branches this hides the SLSR bug.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk
sofar.
Richard.
2019-01-23
Hi.
The PR is about a verification error where we have a FALLTHRU edge that
contains barrier instruction. The instruction is created during bbpart pass
in add_labels_and_missing_jumps (emit_barrier_after_bb). At that time, the
basic blocks live in a different partition (hot,cold). Later then the
On 22/01/2019 15:46, Jakub Jelinek wrote:
> On Tue, Jan 22, 2019 at 02:43:38PM +, Richard Earnshaw (lists) wrote:
>> PR target/88469
>> * profile-count.h (profile_count): Add dummy file with 64-bit alignment
>> on arm-based systems using gcc-6/7/8.
>>
>
>> diff --git
Hi,
this is a regression present in Ada on the mainline since we switched to using
the internal support for thunks: expand_thunk segfaults during inlining when
trying to access the DECL_RESULT of the special alias built to make the call
from the thunk local, if the DECL_RESULT of the thunk is
Hi.
The patch fixes path creation for situations when a filename.gcda
starts with e.g. '..'.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
I'll install the patch in few days.
Thanks,
Martin
gcc/ChangeLog:
2019-01-23 Martin Liska
PR gcov-profile/88994
From: Xiong Hu Luo
The 5 new builtins vec_sbox_be, vec_cipher_be, vec_cipherlast_be, vec_ncipher_be
and vec_ncipherlast_be only support vector unsigned char type parameters.
Add new instruction crypto_vsbox_ and crypto__ to handle
them accordingly, where the new mode CR_vqdi can be expanded to
Hi All,
This patch adds the documentation for Stack clash protection and Armv8.3-a
support to
changes.html for GCC 9.
I have validated the html using the W3C validator.
Ok for cvs?
Thanks,
Tamar
--
Index: htdocs/gcc-9/changes.html
(Oops, added the wrong email out of habit to the first reply :-))
On Tue, Jan 22, 2019 at 08:37:25PM +0100, Iain Buclaw wrote:
> > diff --git a/gcc/d/d-builtins.cc b/gcc/d/d-builtins.cc
> > index b0a315a3ed9..ca105c7635d 100644
> > --- a/gcc/d/d-builtins.cc
> > +++ b/gcc/d/d-builtins.cc
> > @@
On Wed, Jan 23, 2019 at 10:48 AM Eric Botcazou wrote:
>
> Hi,
>
> this is a regression present in Ada on the mainline since we switched to using
> the internal support for thunks: expand_thunk segfaults during inlining when
> trying to access the DECL_RESULT of the special alias built to make the
On 14/01/2019 10:43, Kyrill Tkachov wrote:
>
> On 08/01/19 11:38, Sam Tebbs wrote:
>>
>> On 1/7/19 6:28 PM, James Greenhalgh wrote:
>> > On Fri, Dec 21, 2018 at 09:00:10AM -0600, Sam Tebbs wrote:
>> >> On 11/9/18 11:04 AM, Sam Tebbs wrote:
>> >
>> >
>> >
>> >> Attached is an improved patch with
FSTYPE FUNC (DWtype u) in libgcc2.c, which converts DI/TI to SF/DF, has
/* No leading bits means u == minimum. */
if (count == 0)
return -(Wtype_MAXp1_F * (Wtype_MAXp1_F / 2));
in the third case (where actually count == 0 only means the high part is
minimum). It should be:
/* No
Hi Steve,
>
> Hi Steve,
>
> No we are using aarch64_be-*-* but this is the only one that popped up as a
> failure which is why I didn't change the others.
> But now I'm wondering why... I'll check the log file manually tomorrow to be
> sure.
I've checked and the reason this didn't show up is
Hi,
dg-extract-results currently moves lines like
WARNING: program timed out
at the end of each .exp section when it generates .sum files.
This is because it sorts its output based on the 2nd field, which is
normally the testname as in:
FAIL: gcc.c-torture/execute/20020129-1.c -O2 -flto
On Wed, Jan 23, 2019 at 11:30:29AM +, Jonny Grant wrote:
> Not a member of this list, please include my email address in any replies.
>
>
> 2019-01-23 Jonny Grant
>
> PR 89010
PR sanitizer/89010
is what should be used.
> * libsanitizer/README.gcc: Update to current
Not a member of this list, please include my email address in any replies.
2019-01-23 Jonny Grant
PR 89010
* libsanitizer/README.gcc: Update to current https URLs
Index: trunk/libsanitizer/README.gcc
===
---
Hi David,
On 18.01.2019 19:58, David Malcolm wrote:
> On Fri, 2019-01-18 at 12:32 -0500, David Malcolm wrote:
>
> [CCing Abel]
>
>> PR rtl-optimization/88423 reports an ICE within sched-ebb.c's
>> begin_move_insn, failing the assertion at line 175, where there's
>> no fall-through edge:
>>
>>
On Wed, 2019-01-23 at 16:52 +0300, Alexander Monakov wrote:
> On Wed, 23 Jan 2019, Andrey Belevantsev wrote:
>
> > For that, I'm not sure. Your patch will leave the tablejump
> > unscheduled at
> > all, i.e. any fields like INSN_TICK would be unfilled and thus the
> > later
> > passes like
On Wed, Jan 23, 2019 at 1:54 PM Jason Merrill wrote:
>
> Since in r265788 I made cxx_eval_outermost_constant_expr more insistent that
> the returned value have the right type, it became more important that
> initialized_type be correct. These two PRs were cases of it giving the wrong
> answer.
On Wed, 2019-01-23 at 23:53 +0100, Jakub Jelinek wrote:
> External Email
>
> ---
> ---
> On Wed, Jan 23, 2019 at 09:56:21PM +, Steve Ellcey wrote:
> > I wonder if we even need to pass a string to the target
> > hook. Instead
> >
Ping: https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00969.html
This patch fixes a couple of P2 regressions. It was first submitted
last summer and mostly reviewed by Jeff but then slipped through
the cracks. Can someone pick it up in Jeff's absence?
On 1/16/19 5:41 PM, Martin Sebor wrote:
On
Here's an updated diff. Still a work in progress, ran the tests for
strings/capacity in both modes, passing now. I am running all the tests in
both modes as well, but will take a while to get results. In the meanwhile I
thought I'd send this out...
Also, that code works on all released
On Wed, Jan 23, 2019 at 5:18 PM Nikhil Benesch wrote:
>
> 2018-01-23 Nikhil Benesch
>
> PR go/89019
> * go-gcc.cc (Gcc_backend::placeholder_struct_type): Mark
> placeholder structs as requiring structural equality.
> (Gcc_backend::set_placeholder_pointer_type):
On Wed, Jan 23, 2019 at 09:56:21PM +, Steve Ellcey wrote:
> I wonder if we even need to pass a string to the target hook. Instead
> of:
>
> !GCC$ builtin (cos) attributes simd (notinbranch) if('x86_64-linux-gnu')
>
> We just have:
>
> !GCC$ builtin (cos) attributes simd (notinbranch)
This patch fixes an ICE I reported earlier today as PR go/89019, which
occurs when compiling sufficiently complicated Go code with link-time
optimization (i.e., -flto) enabled.
Both of these simple test programs are sufficient to trigger the ICE:
$ cat crash1.go
package main
type
From: Xiong Hu Luo
commited in r268228.
---
ChangeLog
2019-01-24 Xiong Hu Luo
* ChangeLog: replace space with tab.
* MAINTAINERS: delete 1 tab to keep alignment.
---
ChangeLog | 4 ++--
MAINTAINERS | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff
On Wed, 23 Jan 2019, Martin Sebor wrote:
> Ping: https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00969.html
This patch is OK.
--
Joseph S. Myers
jos...@codesourcery.com
From: Xiong Hu Luo
commited in 268229.
---
gcc/ChangeLog
2019-01-24 Xiong Hu Luo
* tree-ssa-dom.c (test_for_singularity): fix a comment typo.
* vr-values.c (find_case_label_ranges): fix a comment typo.
---
gcc/tree-ssa-dom.c | 2 +-
gcc/vr-values.c| 2 +-
2 files
On Jan 21, 2019, Jason Merrill wrote:
> "does this have its own template arguments, not just the ones from its
> enclosing class?"
> Perhaps compare the number of levels of template arguments of the
> function to that of its enclosing context?
Is this the logic you had in mind? Or can we
On 1/23/19 4:22 PM, Jakub Jelinek wrote:
> On Tue, Jan 22, 2019 at 02:10:38PM +, Bernd Edlinger wrote:
>> --- gcc/c-family/c-warn.c(revision 268119)
>> +++ gcc/c-family/c-warn.c(working copy)
>> @@ -2796,6 +2796,10 @@ check_address_or_pointer_of_packed_membe
>>if (context)
>>
On Thu, Jan 24, 2019 at 06:39:22AM +, Bernd Edlinger wrote:
> --- gcc/c-family/c-warn.c (revision 268195)
> +++ gcc/c-family/c-warn.c (working copy)
> @@ -2725,14 +2725,18 @@ static tree
> check_address_or_pointer_of_packed_member (tree type, tree rhs)
> {
>bool rvalue = true;
>
This patch by Cherry Zhang changes the libgo runtime to install a
SIGURG handler in c-archive mode. The precise stack scan uses SIGURG
to trigger a stack scan, so we need to have Go signal handler
installed for SIGURG. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to
Hi Steve,
Fixed in revision 268231.
This was a copy/paste/modify with the type built in. Have corrected both.
> > tree
> > + gfc_conv_descriptor_elem_len (tree desc)
> > + {
> > + tree tmp;
> > + tree dtype;
> > +
> > + dtype = gfc_conv_descriptor_dtype (desc);
> > + tmp =
79 matches
Mail list logo
