https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88352
--- Comment #2 from Jay ---
The linked bug was amd64. This is x86.
I'm not sure they are the same. Maybe.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80953
--- Comment #22 from Eric Botcazou ---
> I think it is important to find out why there are those differences in line
> numbers. Is libbacktrace broken on Solaris, or not used at all, something
> different?
AFAICS they only occur with
Hi!
On (at least some of these) tests and on some targets, GCC prints messages
like:
./cc1 -quiet -O3 -fopt-info-vec-optimized -mvis vect-ivdep-1.c
vect-ivdep-1.c:11:3: optimized: loop vectorized using 8 byte vectors
vect-ivdep-1.c:11:3: optimized: loop versioned for vectorization to enhance
Hi!
If we consider -fno-delete-null-pointer-checks as a way to support e.g. AVR
and other targets which can validly place objects at NULL rather than a way
to workaround UBs in code, I believe the following testcase must pass if
there is e.g.
char a[32]; // And this object ends up at
Hi!
This is my proposal for fixing this PR, just a heuristics when optimizing
successive divides might not be a good idea (first testcase), and includes
Marc's testcases which showed cases where optimizing successive divides is a
good idea even if the inner divide is not a single use.
Hi!
The following patch handles clobber stmts the same how we handle them in
convert_local_reference_stmt, if it is the clobber with decl on the lhs and
that lhs needs to be replaced by a field inside of a structure, the clobber
is replaced by GIMPLE_NOP.
Bootstrapped/regtested on x86_64-linux
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86121
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
On Thu, Dec 6, 2018 at 9:31 AM wuyuan (E) wrote:
>
> Hi ARM maintainers:
> The taishanv110 core uses generic pipeline scheduling, which
> restricted the performance of taishanv110 core. By adding the pipeline
> scheduling of taishanv110 core in GCC,The performance of taishanv110 has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86497
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84251
Jeffrey A. Law changed:
What|Removed |Added
CC||no...@turm-lahnstein.de
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86973
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87075
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88383
Martin Sebor changed:
What|Removed |Added
Keywords||patch
Summary|ICE calling
The __builtin_has_attribute function fails with an ICE when
its first argument is an expression such as INDIRECT_REF, or
many others. The code simply assumes it's either a type or
a decl. The attached patch corrects this oversight.
While testing the fix I also noticed the C++ front end expects
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88384
Martin Sebor changed:
What|Removed |Added
Keywords||wrong-code
--- Comment #2 from Martin
Hi!
On Tue, Dec 04, 2018 at 03:30:47PM +, Richard Sandiford wrote:
> Segher Boessenkool writes:
> Hmm, so we allow top-level "asm volatile" in C++ but not C?
Apparently. Evert top-level asm is effectively volatile, so this doesn't
really matter; but should we try to resolve the
++
Assignee: unassigned at gcc dot gnu.org
Reporter: s...@li-snyder.org
Target Milestone: ---
hi -
gcc 20181205 gets an ICE compiling this code. (8.2.1 compiles it without
error.)
thanks,
sss
--
template
struct xtest
On 12/4/18 9:04 AM, Fritz Reese wrote:
On Tue, Dec 4, 2018 at 10:12 AM Jakub Jelinek wrote:
Just a couple of random comments.
-fdec-pad-with-spaces option name doesn't look right, because it doesn't say
what the option affects. So perhaps have transfer in the option name?
[...]
Wouldn't it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88384
Martin Sebor changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88384
Bug ID: 88384
Summary: __alignof__ of an rvalue is different between C and
C++
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Hi ARM maintainers:
The taishanv110 core uses generic pipeline scheduling, which restricted
the performance of taishanv110 core. By adding the pipeline scheduling of
taishanv110 core in GCC,The performance of taishanv110 has been improved.
The patch as follows, please join.
On 11/16/18 5:32 PM, Alexandre Oliva wrote:
When binding an object to a template parameter of reference type, we
take the address of the object and dereference that address. The type
of the address may still carry (template) typedefs, but
verify_unstripped_args_1 rejects such typedefs other
On 11/16/18 5:32 PM, Alexandre Oliva wrote:
When a member template is redeclared as a friend, we enter the context
of the member before looking it up, and then we check that the decls
are compatible. However, when the member template references template
types of the enclosing context, say an
On 11/16/18 3:50 PM, Jakub Jelinek wrote:
On Fri, Nov 16, 2018 at 10:01:05AM -0500, Nathan Sidwell wrote:
2018-11-16 Nathan Sidwell
PR c++/87269
* parser.c (lookup_literal_operator): Mark overload for keeping
when inside template. Refactor.
*
On 11/16/18 9:16 PM, Alexandre Oliva wrote:
We used to preserve deferred access check along with resolved template
ids, but a tentative parsing firewall introduced additional layers of
deferred access checks, so that we don't preserve the checks we
want to any more.
This patch collapses the
On 12/3/18 5:54 PM, David Malcolm wrote:
I was going to ping this patch:
https://gcc.gnu.org/ml/gcc-patches/2018-11/msg00875.html
but it has bit-rotted somewhat, so here's a refreshed version of it.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
OK for trunk?
Thanks
Dave
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85770
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
PR85770 is fixed by Segher's combiner patch to avoid combining hard
regs. Presumably it helps because it gives the allocators more freedom.
I'm adding the testcase from the PR to the regression suite.
Jeff
commit 40fc691eac0ea9414f7908826c91afc70ff78617
Author: law
Date: Thu Dec 6 00:40:08
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85770
--- Comment #5 from Jeffrey A. Law ---
Author: law
Date: Thu Dec 6 00:40:08 2018
New Revision: 266839
URL: https://gcc.gnu.org/viewcvs?rev=266839=gcc=rev
Log:
PR rtl-optimization/85770
* gcc.target/i386/pr85770.c: New test.
On Wed, Dec 05, 2018 at 04:48:28PM -0500, Fritz Reese wrote:
> On Wed, Dec 5, 2018 at 12:00 AM Steve Kargl
> wrote:
> >
> > I intend to commit the attached patch on Saturday.
>
> Thanks for the work. I assume the patch bootstraps and passes
> regression tests?
The patch passed regression
On 12/5/18 1:56 PM, Uros Bizjak wrote:
> This macro is always defined through defaults.h. We can remove #ifdef
> check from dwarf2out.c
>
> 2018-12-05 Uros Bizjak
>
> * dwarf2out.c (field_byte_offset): Remove
> #ifdef PCC_BITFIELD_TYPE_MATTERS check.
>
> Bootstrapped and regression
On Tue, 4 Dec 2018 14:55:03 +0100
Richard Biener wrote:
> On Tue, 4 Dec 2018, Jakub Jelinek wrote:
>
> > On Mon, Dec 03, 2018 at 11:40:39PM +, Julian Brown wrote:
> > > Jakub asked in the following email at the time of the patch
> > > submission for the gomp4 branch what the difference
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85770
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
--- Comment #4
Thanks, I'll check them out.
On Thu 6 Dec, 2018, 1:51 AM Eric Gallager, wrote:
> On 12/5/18, David Malcolm wrote:
> > On Wed, 2018-12-05 at 22:48 +0530, Durgesh Kumar wrote:
> >> Dear sir/mam
> >> I am durgesh kumar from ABES engineering collenge,ghaziabad,uttar
> >> pradesh,india.
> >>
> >> I
Hi, Honza,
I have one question relate to whether to disable nothrow for -flive-patching as
following:
actually, there are two passes here:
1. local nothrow pass: in this pass, nothrow attribute is set locally after
analyzing every stmt of the function
body:
unsigned int
On 11/29/18 4:43 PM, Martin Sebor wrote:
> On 11/29/18 4:07 PM, Jeff Law wrote:
>> On 11/29/18 1:34 PM, Martin Sebor wrote:
>>> On 11/16/2018 02:07 AM, Richard Biener wrote:
On Fri, Nov 16, 2018 at 4:12 AM Martin Sebor wrote:
>
> Ping:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87028
Jeffrey A. Law changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
This libgo patch by Cherry Zhang adds support for precise stack
scanning to the Go runtime. This uses per-function stack maps stored
in the exception tables in the language-specific data area. The
compiler needs to generate these stack maps; currently this is only
done by a version of LLVM, not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87028
--- Comment #8 from Jeffrey A. Law ---
Author: law
Date: Wed Dec 5 23:10:08 2018
New Revision: 266833
URL: https://gcc.gnu.org/viewcvs?rev=266833=gcc=rev
Log:
PR c/87028
* calls.c (get_attr_nonstring_decl): Avoid setting *REF
Hi!
On Wed, Dec 05, 2018 at 04:47:37PM -0500, Jason Merrill wrote:
> On 12/2/18 11:38 AM, Segher Boessenkool wrote:
> >PR55681 observes that currently only one qualifier is allowed for
> >inline asm, so that e.g. "volatile asm" is allowed, "const asm" is also
> >okay (with a warning), but "const
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88383
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
On 12/5/18 5:34 PM, Paolo Carlini wrote:
Hi,
On 05/12/18 20:31, Jason Merrill wrote:
On 12/5/18 7:45 AM, Paolo Carlini wrote:
Hi,
as mentioned in one of my last patches, we can now improve this
location. Note: in the same function there are a few further issues
which I mean to
On 11/21/18 7:19 AM, Tobias Burnus wrote:
Hello all,
if a class contains any 'virtual ... = 0', it's an abstract class and for an
abstract class, the destructor not added to the vtable.
For a normal
virtual ~class() { }
that's not a problem as the class::~class() destructor will be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88383
Bug ID: 88383
Summary: ICE calling _builtin_has_attribute(r, aligned(N))) on
an overaligned reference r
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88362
--- Comment #7 from Martin Sebor ---
I would think for the same reason why attribute aligned applies to the
reference and not to the type it refers to. If it makes sense for the
following to declare an overaligned reference to an ordinary int
Hi,
On 05/12/18 20:31, Jason Merrill wrote:
On 12/5/18 7:45 AM, Paolo Carlini wrote:
Hi,
as mentioned in one of my last patches, we can now improve this
location. Note: in the same function there are a few further issues
which I mean to incrementally fix (eg, the diagnostics for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88382
Bug ID: 88382
Summary: undocumented GNU C extension: C++ raw string literals
permitted in GNU C
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
On Wed, Dec 5, 2018 at 12:00 AM Steve Kargl
wrote:
>
> I intend to commit the attached patch on Saturday.
Thanks for the work. I assume the patch bootstraps and passes regression tests?
RE:
> PR fortran/88228
> * expr.c (check_null, check_elemental): Work around -fdec and
>
Ping.
This is a ping of my patch set to implement the SIMD ABI on Aarch64.
https://gcc.gnu.org/ml/gcc-patches/2018-11/msg00636.html
https://gcc.gnu.org/ml/gcc-patches/2018-11/msg00637.html
https://gcc.gnu.org/ml/gcc-patches/2018-11/msg00639.html
On 12/2/18 11:38 AM, Segher Boessenkool wrote:
PR55681 observes that currently only one qualifier is allowed for
inline asm, so that e.g. "volatile asm" is allowed, "const asm" is also
okay (with a warning), but "const volatile asm" gives an error. Also
"goto" has to be last.
This patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88381
Bug ID: 88381
Summary: __builtin_thread_pointer missing documentation,
defined as implicit_p
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
On Tue, 4 Dec 2018 15:02:15 +0100
Jakub Jelinek wrote:
> On Tue, Aug 28, 2018 at 03:19:19PM -0400, Julian Brown wrote:
> > 2018-08-28 Julian Brown
> > Cesar Philippidis
> >
> > PR middle-end/70828
> >
> > gcc/
> > * gimplify.c (gimplify_omp_ctx): Add decl_data_clause
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88364
--- Comment #3 from Thomas Koenig ---
Probably easiest to omit the clobber if there is a reference.
This macro is always defined through defaults.h. We can remove #ifdef
check from dwarf2out.c
2018-12-05 Uros Bizjak
* dwarf2out.c (field_byte_offset): Remove
#ifdef PCC_BITFIELD_TYPE_MATTERS check.
Bootstrapped and regression tested on x86_64-linux-gnu {,-m32}.
OK for mainline?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88362
--- Comment #6 from joseph at codesourcery dot com ---
On Wed, 5 Dec 2018, msebor at gcc dot gnu.org wrote:
> so that we get consistent behavior for reference members. __alignof__ should
> return the corresponding alignment. For example, in
On Wed, Dec 05, 2018 at 03:49:26PM -0500, Jason Merrill wrote:
> On 11/28/18 3:42 AM, Jakub Jelinek wrote:
> > Whenever we need to clone a cdtor (either because the target doesn't support
> > aliases the way we need, e.g. initlist105.C testcase on darwin, where it has
> > been originally reported,
On 11/28/18 3:42 AM, Jakub Jelinek wrote:
Whenever we need to clone a cdtor (either because the target doesn't support
aliases the way we need, e.g. initlist105.C testcase on darwin, where it has
been originally reported, or when it has virtual bases, like the made up
initlist106.C on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52869
--- Comment #12 from Jonathan Wakely ---
The exception specification seems to be processed too early, before the other
class members are in scope. This slight variation of comment 5 still fails on
trunk:
struct S {
void g()
GROUP_BITFIELDS_BY_ALIGN was long gone, PCC_BITFIELD_TYPE_MATTERS
defaults to 1 in i386.h for all x86 targets.
2018-12-05 Uros Bizjak
* config/i386/cygming.h (PCC_BITFIELD_TYPE_MATTERS): Remove.
(GROUP_BITFIELDS_BY_ALIGN): Ditto.
Tested by building crosscompiler to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88320
David Malcolm changed:
What|Removed |Added
Keywords||patch
URL|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
seurer at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
PR c++/88320 reports that the C and C++ FEs can offer bogus suggestions
for misspelled identifiers within initializers, where the thing being
initialized is suggested. If the user follows these suggestions,
it will lead to a -Wuninitialized warning. For example:
test.c:9:19: error: 'aresults'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88380
Bug ID: 88380
Summary: Sequence of not-explicitly initialised, initialised,
variable length generates no initialiser
Product: gcc
Version: 9.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88064
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87531
petschy at gmail dot com changed:
What|Removed |Added
CC||petschy at gmail dot com
---
On 12/5/18, David Malcolm wrote:
> On Wed, 2018-12-05 at 22:48 +0530, Durgesh Kumar wrote:
>> Dear sir/mam
>> I am durgesh kumar from ABES engineering collenge,ghaziabad,uttar
>> pradesh,india.
>>
>> I am currently in 2nd year of my graduation(Btech CSE )
>>
>> I want to contribute in some of
On 12/5/18 12:13 PM, Jeff Law wrote:
On 12/5/18 11:59 AM, David Edelsohn wrote:
Jeff,
Thanks for the patch.
I continue to see a failure on AIX 32 bit mode (2 byte wchar).
FAIL: gcc.dg/strlenopt-58.c scan-tree-dump-times optimized
"call_in_true_branch_not_eliminated" 0
I'm not certain if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87350
--- Comment #6 from Bernhard Kaindl ---
Created attachment 45167
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45167=edit
Safe fix: Before copying work, check if the vectors have been allocated. If
not, input wasn't valid.
Fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88357
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88357
--- Comment #6 from G. Steinmetz ---
Sure, this is now pr88379.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88379
Bug ID: 88379
Summary: ICE in resolve_assoc_var, at fortran/resolve.c:8750
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
--- Comment #11 from pkoning at gcc dot gnu.org ---
Thanks, I had forgotten.
Seurer, could you update to r265741 or later and check if that cures the issue?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87350
Bernhard Kaindl changed:
What|Removed |Added
CC||bernhard.kaindl@thalesgroup
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
--- Comment #10 from Segher Boessenkool ---
You have
/* { dg-error "alignment of 's' is greater" "" { target pdp11*-*-* } } */
(the "" was added in r265741, the source tree I looked at wasn't up-to-date).
dg.exp says this is
# dg-error regexp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85569
Pavel Roskin changed:
What|Removed |Added
CC||proski at gnu dot org
--- Comment #11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88359
--- Comment #7 from Geert linders ---
Hi Pinskia,
Which minimum version of avr-gcc is suitable?
Cheers - Geert
From: pinskia at gcc dot gnu.org
Sent: Wednesday, 5 December 2018 10:21
To: geert.lind...@hotmail.com
Subject: [Bug
Hi,
I'm trying to write a testcase to reproduce duplicate clone symbols
such as in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88297 I
started with a testcase that is known to have constprop clones and
split it into two object files:
bash-4.2# cat
On 12/5/18 7:45 AM, Paolo Carlini wrote:
Hi,
as mentioned in one of my last patches, we can now improve this
location. Note: in the same function there are a few further issues
which I mean to incrementally fix (eg, the diagnostics for
warn_if_not_aligned ICEs for unnamed bit-fields). Tested
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88372
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On 12/5/18 11:59 AM, David Edelsohn wrote:
> Jeff,
>
> Thanks for the patch.
>
> I continue to see a failure on AIX 32 bit mode (2 byte wchar).
>
> FAIL: gcc.dg/strlenopt-58.c scan-tree-dump-times optimized
> "call_in_true_branch_not_eliminated" 0
>
> I'm not certain if this is AIX-specific or
Jeff,
Thanks for the patch.
I continue to see a failure on AIX 32 bit mode (2 byte wchar).
FAIL: gcc.dg/strlenopt-58.c scan-tree-dump-times optimized
"call_in_true_branch_not_eliminated" 0
I'm not certain if this is AIX-specific or more fallout from wchar
size. I could ignore with target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88359
--- Comment #6 from Geert linders ---
Hi Pinskia,
Which minimum version of avr-gcc is suitable?
Cheers - Geert
From: pinskia at gcc dot gnu.org
Sent: Wednesday, 5 December 2018 10:21
To:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88357
--- Comment #5 from kargl at gcc dot gnu.org ---
(In reply to G. Steinmetz from comment #4)
> Thanks for working on these issues.
Gerhard,
Can you migrate z2.f90 to its own PR? It is going to
require much more effort to fix. My first attempt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88367
--- Comment #8 from Jakub Jelinek ---
Created attachment 45166
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45166=edit
gcc9-pr88367.patch
Possible untested patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88378
Bug ID: 88378
Summary: notes for template deduction errors mention "[with U =
U]"
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Hi Chung-Lin,
> > +module openacc_c_string
> > + implicit none
> > +
> > + interface
> > +function strlen (s) bind (C, name = "strlen")
> > + use iso_c_binding, only: c_ptr, c_size_t
> > + type (c_ptr), intent(in), value :: s
> > + integer (c_size_t) :: strlen
> > +end
On Wed, Dec 05, 2018 at 05:10:07PM +, Iain Sandoe wrote:
> Hi,
>
> The PR is about unnecessary saves of the pic base register, it shows on m32
> Linux and m32/m64 Darwin.
>
> The fix is to check that we are in a pic mode and that the picbase has
> actually been used.
> As a bonus, some
On Wed, Dec 05, 2018 at 11:37:27AM -0600, Segher Boessenkool wrote:
> On Wed, Dec 05, 2018 at 10:04:56AM +, Richard Sandiford wrote:
> > Martin Sebor writes:
> > > Martin suggested we update the Coding Conventions to describe
> > > the expected style for function declarations with a pointer
>
On 12/5/18 3:04 AM, Richard Sandiford wrote:
Thanks for doing this,
Martin Sebor writes:
Martin suggested we update the Coding Conventions to describe
the expected style for function declarations with a pointer
return types, and for overloaded operators. Below is the patch.
As an aside,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88376
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88362
--- Comment #5 from Martin Sebor ---
I think the attribute on references needs to work the same way as on pointers
so that we get consistent behavior for reference members. __alignof__ should
return the corresponding alignment. For example, in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87615
--- Comment #11 from Martin Jambor ---
It's actually, ipa_polymorphic_call_context::get_dynamic_type that causes
problems here. I'll prepare a patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88146
--- Comment #8 from Alexandre Oliva ---
So, no, it's not a copy ctor, but apparently we're reusing the logic that
synthesizes them for other non-default ctors.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88367
--- Comment #7 from Jakub Jelinek ---
In GCC 8 we had:
else if (code == POINTER_PLUS_EXPR)
{
/* For pointer types, we are really only interested in asserting
whether the expression evaluates to non-NULL. */
On Wed, 5 Dec 2018, Segher Boessenkool wrote:
> Patches are usually ignored because everyone thinks someone else will
> handle it.
And in this case, it looks like this patch would best be reviewed first in
the GDB context - then once committed to binutils-gdb, the committer could
post to
On Wed, Dec 05, 2018 at 10:04:56AM +, Richard Sandiford wrote:
> Martin Sebor writes:
> > Martin suggested we update the Coding Conventions to describe
> > the expected style for function declarations with a pointer
> > return types, and for overloaded operators. Below is the patch.
> >
> >
On Wed, 2018-12-05 at 22:48 +0530, Durgesh Kumar wrote:
> Dear sir/mam
> I am durgesh kumar from ABES engineering collenge,ghaziabad,uttar
> pradesh,india.
>
> I am currently in 2nd year of my graduation(Btech CSE )
>
> I want to contribute in some of your prestigious project. So i
> request you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88320
--- Comment #9 from Jonny Grant ---
(In reply to David Malcolm from comment #8)
> FWIW, clang trunk currently gives the same erroneous suggestion:
>
> :4:19: error: use of undeclared identifier 'aresults'; did you mean
> 'aresult'?
> int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
--- Comment #9 from pkoning at gcc dot gnu.org ---
Comment? I thought the comment is the null string after the regexp to match.
Should it read { target { pdp11-*-* } } with the extra braces?
Other examples show up both with the braces and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88377
Bug ID: 88377
Summary: ICE in gfc_omp_clause_copy_ctor, at
fortran/trans-openmp.c:614
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
1 - 100 of 234 matches
Mail list logo
