https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81192
Tom de Vries changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80117
--- Comment #25 from Timo Teräs ---
(In reply to Andrew Pinski from comment #24)
> >This works everywhere else, so I wonder if we could have the ada makefile
> >check the abi somehow more reliably than pathname?
>
> Your patch is broken
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81192
--- Comment #19 from Tom de Vries ---
Author: vries
Date: Thu Jul 13 05:42:15 2017
New Revision: 250175
URL: https://gcc.gnu.org/viewcvs?rev=250175=gcc=rev
Log:
Backport "Fix sigsegv in find_same_succ_bb"
2017-07-13 Tom de Vries
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80117
--- Comment #24 from Andrew Pinski ---
>This works everywhere else, so I wonder if we could have the ada makefile
>check the abi somehow more reliably than pathname?
Your patch is broken anyways because it makes your OS very incompatible with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80117
--- Comment #23 from Timo Teräs ---
(In reply to Andrew Pinski from comment #22)
> (In reply to Timo Teräs from comment #21)
> > This caused a regression for non-multilib builds. Now my non-multilib lp64
> > build fails with:
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80117
--- Comment #22 from Andrew Pinski ---
(In reply to Timo Teräs from comment #21)
> This caused a regression for non-multilib builds. Now my non-multilib lp64
> build fails with:
> a-cfinve.ads:245:04: warning: in instantiation at a-coboho.adb:55
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80117
Timo Teräs changed:
What|Removed |Added
CC||timo.teras at iki dot fi
--- Comment #21
On 05/07/2017 18:10, Jonathan Wakely wrote:
On 19/06/17 22:48 +0200, François Dumont wrote:
Hi
Here is the patch to default the default and move constructors on
the std::forward_list. Putting a move constructor on
_Fwd_list_node_base helped limiting the code impact of this patch. It
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81296
Jerry DeLisle changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot
gnu.org
On Wed, Jul 12, 2017 at 9:10 PM, Marc Glisse wrote:
> On Wed, 12 Jul 2017, Andrew Pinski wrote:
>
>> Hi,
>> Unlike most other expressions, BIT_INSERT_EXPR has an implicit
>> operand of the precision/size of the second operand. This means if we
>> have an integer constant
On Wed, 12 Jul 2017, Andrew Pinski wrote:
Hi,
Unlike most other expressions, BIT_INSERT_EXPR has an implicit
operand of the precision/size of the second operand. This means if we
have an integer constant for the second operand and that compares to
the same constant value, vn_nary_op_eq would
On Wed, 2017-07-12 at 08:57 -0600, Sandra Loosemore wrote:
> On 07/12/2017 05:07 AM, Klaus Kruse Pedersen (Klaus) wrote:
> > I have seen reproducible builds being discussed here, but what is
> > the
> > position on inter c-lib and OS reproducible builds?
>
> I think we consider unstable sort
On 07/12/2017 06:31 PM, Segher Boessenkool wrote:
> Hi!
>
> On Tue, Jul 11, 2017 at 03:19:57PM -0600, Jeff Law wrote:
>> It introduces a new style of stack probing -fstack-check=clash,
>> including documentation of the new option, how it differs from
>> -fstack-check=specific, etc.
>>
>> FWIW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81393
Ian Lance Taylor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
On Wed, Jul 12, 2017 at 7:44 AM, Andreas Krebbel
wrote:
>
> ptrace SETREGS and GETREGS were never supported on S/390. The macros
> were accidentally defined in the Glibc header though. A recent Glibc
> change removed them breaking libgo build on S/390.
>
> This patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81393
--- Comment #3 from ian at gcc dot gnu.org ---
Author: ian
Date: Thu Jul 13 03:44:14 2017
New Revision: 250174
URL: https://gcc.gnu.org/viewcvs?rev=250174=gcc=rev
Log:
PR go/81393
syscall: don't use GETREGS/SETREGS on s390
They
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65757
Jerry DeLisle changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64867
John Steele Scott changed:
What|Removed |Added
CC||toojays at toojays dot net
---
On Tue, Jul 11, 2017 at 03:20:12PM -0600, Jeff Law wrote:
> * conifg/mips/mips.c (mips_expand_prologue): Likewise.
Typo ("conifg").
> --- a/gcc/defaults.h
> +++ b/gcc/defaults.h
> @@ -1408,8 +1408,11 @@ see the files COPYING3 and COPYING.RUNTIME
> respectively. If not, see
> #endif
>
Hi,
Unlike most other expressions, BIT_INSERT_EXPR has an implicit
operand of the precision/size of the second operand. This means if we
have an integer constant for the second operand and that compares to
the same constant value, vn_nary_op_eq would return that these two
expressions are the
Hi!
On Tue, Jul 11, 2017 at 03:19:57PM -0600, Jeff Law wrote:
> It introduces a new style of stack probing -fstack-check=clash,
> including documentation of the new option, how it differs from
> -fstack-check=specific, etc.
>
> FWIW -fstack-check=specific is dreadfully named. I haven't tried to
I am looking into reversing loop to increased efficiency. There is
already a PR22041 for this and an old patch
https://gcc.gnu.org/ml/gcc-patches/2006-01/msg01851.html by Zdenek
which never made it to mainline.
For constant loop count, ivcanon pass is adding reverse iv but this
not selected by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81423
Bug ID: 81423
Summary: Wrong code at -O2
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Hmmm, I didn't realize that gcc 6.x also supported __builtin_cpu_*. I imagine
we will need backports there as well.
--
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meiss...@linux.vnet.ibm.com, phone: +1 (978) 899-4797
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81193
--- Comment #13 from Michael Meissner ---
Author: meissner
Date: Wed Jul 12 23:07:50 2017
New Revision: 250165
URL: https://gcc.gnu.org/viewcvs?rev=250165=gcc=rev
Log:
[gcc]
2017-07-12 Michael Meissner
GCC Maintainers:
The following patch adds support for the vec_extract_fp_from_shorth()
and vec_extract_fp_from_short builtin functions. The patch has been
tested on powerpc64le-unknown-linux-gnu (Power 8 LE) and
powerpc64le-unknown-linux-gnu (Power 9 LE). The test generates 1
unsupported test on
On Tue, Jul 11, 2017 at 03:19:36PM -0600, Jeff Law wrote:
> Examples of implicit probes include
> 2. ABI mandates that *sp always contain a backchain pointer (ppc)
In the ELFv2 ABI a backchain is not required. GCC still always has
one afaik. I'll find out more.
> To get a sense of overhead,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81421
--- Comment #1 from Ian Lance Taylor ---
I can't recreate this and nobody else has reported it. runtime.lo should not
depend on runtime.s-gox.
What are the contents of BUILDDIR/TARGET/libgo/runtime.lo.dep?
Thank you for the fix and the cleanup, Jeff!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70570
--- Comment #3 from Jesse Haber-Kucharsky ---
The .ii file is too large to attach. I hope the previous information I supplied
is sufficient and helpful.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81422
Bug ID: 81422
Summary: [aarch64] internal compiler error: in
update_equiv_regs, at ira.c:3425
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70570
Jesse Haber-Kucharsky changed:
What|Removed |Added
CC||jhaberku at scylladb dot com
My tester has been complaining regularly for a little while WRT the
riscv port failing to build due minor header file goof's.
While just reordering the headers is sufficient to fix one of the two
problems, I took the opportunity to remove > 50 unnecessary includes
from riscv.c.
The second
On Wed, Jul 12, 2017 at 01:34:01PM -0500, Bill Schmidt wrote:
> Although I said this was invalid code, it really isn't -- it's legal code.
> It's more of an ice-on-stupid-code situation. :) So probably you should
> remove the "invalid" language from the commentary. Sorry for misleading you.
On Wed, Jul 12, 2017 at 11:45:07AM -0500, Will Schmidt wrote:
> diff --git a/gcc/config/rs6000/rs6000.c b/gcc/config/rs6000/rs6000.c
> index 10c5521..e21b56f 100644
> --- a/gcc/config/rs6000/rs6000.c
> +++ b/gcc/config/rs6000/rs6000.c
> @@ -16297,6 +16297,9 @@ rs6000_gimple_fold_builtin
On Wed, Jul 12, 2017 at 04:07:42PM -0500, Segher Boessenkool wrote:
> Hi Mike,
>
> On Wed, Jul 12, 2017 at 11:38:11AM -0400, Michael Meissner wrote:
> > I also changed the current warning in target_clones handling to be an error
> > instead of a warning, since it really makes no sense to use
On 07/12/2017 06:47 AM, Trevor Saunders wrote:
> On Tue, Jul 11, 2017 at 08:02:26PM -0600, Jeff Law wrote:
>> On 07/11/2017 06:20 PM, Wilco Dijkstra wrote:
>>> Jeff Law wrote:
aarch64 is the first target that does not have any implicit probes in
the caller. Thus at prologue entry it
Hi Mike,
On Wed, Jul 12, 2017 at 11:38:11AM -0400, Michael Meissner wrote:
> I also changed the current warning in target_clones handling to be an error
> instead of a warning, since it really makes no sense to use target_clones if
> we
> can't generate a resolver function.
Okay. Another
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81413
--- Comment #1 from Jonathan Wakely ---
The linker model on Windows is weird, there are already existing bugs about
this (at least PR 77726 but others too).
It works fine on other platforms.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81421
Bug ID: 81421
Summary: Circular runtime.s-gox -> runtime.lo dependency
dropped -> objcopy: 'runtime.s-gox.tmp': No such file
Product: gcc
Version: 7.1.0
Status:
On 05/07/2017 17:22, Jonathan Wakely wrote:
It's mostly good, but I'd like to make a few suggestions ...
diff --git a/libstdc++-v3/include/bits/stl_list.h
b/libstdc++-v3/include/bits/stl_list.h
index 232885a..7e5 100644
--- a/libstdc++-v3/include/bits/stl_list.h
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81135
Franklin "Snaipe" Mathieu changed:
What|Removed |Added
CC||snaipe at arista dot com
On 07/12/2017 03:14 PM, Christophe Lyon wrote:
Hi Nathan,
/gccsrc/libcc1/libcp1plugin.cc: In function ‘gcc_decl
plugin_build_decl(cc1_plugin::connection*,
const char*, gcc_cp_symbol_kind, gcc_type, const char*, gcc_address,
const char*, unsigned int)’:
/gccsrc/libcc1/libcp1plugin.cc:1422:
On Wed, Jul 12, 2017 at 03:30:00PM +0200, Georg-Johann Lay wrote:
> On 12.07.2017 14:11, Segher Boessenkool wrote:
> >On Tue, Jul 11, 2017 at 10:47:27AM +0200, Georg-Johann Lay wrote:
> >>This small addition improves costs of PARALLELs in
> >>rtlanal.c:seq_cost(). Up to now, these costs are
>
Hi Nathan,
On 12 July 2017 at 19:34, Nathan Sidwell wrote:
> Now that all the cdtors have special names, we can detect them by looking at
> the name, rather than a collection of other things.
>
> For the DECL_[CD]TOR_P cases we're now comparing identifiers, removing a
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81420
Bug ID: 81420
Summary: When a reference is bound to a member in the base of a
temporary, lifetime of the temporary is not extended
Product: gcc
Version: 8.0
Status:
Although I said this was invalid code, it really isn't -- it's legal code.
It's more of an ice-on-stupid-code situation. :) So probably you should remove
the "invalid" language from the commentary. Sorry for misleading you.
-- Bill
Bill Schmidt, Ph.D.
GCC for Linux on Power
Linux on Power
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81406
--- Comment #2 from David Binderman ---
Created attachment 41738
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41738=edit
preprocessed C source code
Flags -O2 -g -pipe -fexceptions -fstack-protector-strong
--param=ssp-buffer-size=4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81303
Wilco changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Now that all the cdtors have special names, we can detect them by looking at the
name, rather than a collection of other things.
For the DECL_[CD]TOR_P cases we're now comparing identifiers, removing a
STRIP_TEMPLATE
For the IN_CHARGE case we're replacing a conjunction of 3 checks (2 of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81417
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81419
Bug ID: 81419
Summary: GCC wrongly suggests function-like macro as fixit hint
for undefined object-like macro
Product: gcc
Version: 8.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49928
Eric Gallager changed:
What|Removed |Added
CC||egall at gwmail dot gwu.edu
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81418
Bug ID: 81418
Summary: [8 Regression] ICE in vect_get_vec_def_for_stmt_copy
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
On Jul 11 2017, Maxim Ostapenko wrote:
> Ok, I see, it seems that we need to add convert in
> expand_asan_emit_allocas_unpoison too. This patch seems to work for me on
> aarch64 -mabi=ilp32, could you check it as well?
This fixes all regressions.
Andreas.
--
Andreas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81417
Bug ID: 81417
Summary: -Wsign-compare should print types being compared
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Hi,
Do not do the gimple-folding optimizations of expressions that are
missing their LHS. (Preventing an ICE on invalid code).
This was noticed during debug of PR81317, but is not a fix for that PR.
This is based on a patch suggested by Segher.
(This will need a revisit if/when we get
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81416
--- Comment #1 from Andrew Pinski ---
Try increasing your stack limit. I suspect it is too low. With -fopenmp turned
on causes arrays to be always stored on the stack .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59521
Yuri Gribov changed:
What|Removed |Added
Attachment #41698|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81416
Bug ID: 81416
Summary: OpenMP craches if large arrays passed
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
The little-endian VSX code uses rotates to swap the two 64-bit halves of
128-bit scalar modes. This is fine for TImode and V1TImode, but it
isn't really valid to use RTL rotates on floating-point modes like
KFmode and TFmode, and doing that triggered an assert added by the
SVE series. This patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81069
Tom de Vries changed:
What|Removed |Added
Attachment #41733|0 |1
is obsolete|
This patchlet fixes a complaint from translation
projects because some non-quoted key words like
"interrupt" or "signal" caused problems there.
Enclosed the sequence in "WITH_AVRLIBC" because that is
only relevant when AVR-LibC start-up code is in use.
Also warns for functions named "ISR",
From: Franklin “Snaipe” Mathieu
Due to an earlier change in gcc that split the dwarf info generation
in two steps (one early, one late), the DIE for unreferenced extern
globals are no longer removed (in fact, they didn't emit it at
all since they had already processed the
From: Franklin “Snaipe” Mathieu
Due to an earlier change in gcc that split the dwarf info generation
in two steps (one early, one late), the DIE for unreferenced extern
globals are no longer removed (in fact, they didn't emit it at
all since they had already processed the
From: Franklin “Snaipe” Mathieu
Due to an earlier change in gcc that split the dwarf info generation
in two steps (one early, one late), the DIE for unreferenced extern
globals are no longer removed (in fact, they didn't emit it at
all since they had already processed the
From: Franklin “Snaipe” Mathieu
Hello GCC folks,
This patch series addresses PR 81135 [1].
* patch 1/3 is for trunk (built/tested on trunk@250093).
* patch 2/3 is the gcc7 backport (built/tested on gcc-7-branch@249680).
* patch 3/3 is the gcc6 backport (built/tested on
> On Jul 12, 2017, at 10:28 AM, David Miller wrote:
>
> From: Qing Zhao
> Date: Wed, 12 Jul 2017 08:49:52 -0500
>
>> and it also clearly mentioned that “specially aligned memory might
>> use this constraint”.
>
> It guarantees the achieve the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79883
Georg-Johann Lay changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
This patch adds a warning to the built-in function handling if the user used
the __builtin_cpu_supports and __builtin_cpu_is were used when the compiler was
configured to use an old GLIBC that does not provice the hardware capability
bits. Previously, the compiler would silently change the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81415
--- Comment #3 from Steven Pemberton ---
$ gcc --version
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81415
--- Comment #2 from Steven Pemberton ---
Created attachment 41735
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41735=edit
termio2.c Second test case, prints all 17 bindings.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81415
--- Comment #1 from Steven Pemberton ---
This is with the default gcc on Ubuntu 16.04.02
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81415
Bug ID: 81415
Summary: termio ioctl returns incorrect value for some
characters
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
Severity: normal
On 07/11/2017 06:29 AM, Prathamesh Kulkarni wrote:
@@ -6074,6 +6076,12 @@ In C++ enumerated type mismatches in conditional
expressions are also
diagnosed and the warning is enabled by default. In C this warning is
enabled by @option{-Wall}.
+@item -Wenum-conversion @r{(C, Objective-C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79883
--- Comment #8 from Georg-Johann Lay ---
Author: gjl
Date: Wed Jul 12 15:31:22 2017
New Revision: 250157
URL: https://gcc.gnu.org/viewcvs?rev=250157=gcc=rev
Log:
gcc/
Backport from 2017-07-12 trunk r250156.
PR target/79883
From: Qing Zhao
Date: Wed, 12 Jul 2017 08:49:52 -0500
> and it also clearly mentioned that “specially aligned memory might
> use this constraint”.
It guarantees the achieve the opposite of what you are trying to do.
That is, it can be used to guarantee that something is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79883
--- Comment #7 from Georg-Johann Lay ---
Author: gjl
Date: Wed Jul 12 15:25:07 2017
New Revision: 250156
URL: https://gcc.gnu.org/viewcvs?rev=250156=gcc=rev
Log:
PR target/79883
* config/avr/avr.c (avr_set_current_function): In
On 07/06/2017 07:25 AM, Daniel P. Berrange wrote:
There are several hundred named attribute keys that have been
introduced over many GCC releases. Applications typically need
to be compilable with multiple GCC versions, so it is important
for developers to know when GCC introduced support for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81405
David Malcolm changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
Hi,
After change @236817, AArch64 backend could avoid unnecessary conversion
instructions
for register between different modes now. As a result, GCC could initialize
register
in larger mode and use it later in smaller mode. such def-use chain is not
supported
by current regrename.c analyzer,
On 07/12/2017 07:13 AM, Trevor Saunders wrote:
On Tue, Jul 11, 2017 at 11:24:45AM -0400, David Malcolm wrote:
+/* Some tokens naturally come in pairs e.g.'(' and ')'.
+ This class is for tracking such a matching pair of symbols.
+ In particular, it tracks the location of the first token,
+
The attached patch fixes PR81362.
npeel was erroneously overwritten by vect_peeling_hash_get_lowest_cost
although the corresponding dataref is not used afterwards. It should be
safe to get rid of the npeel parameter since we use the returned
peeling_info's npeel anyway. Also removed the
On Wed, Jul 12, 2017 at 3:57 PM, Sandra Loosemore
wrote:
> On 07/12/2017 05:07 AM, Klaus Kruse Pedersen (Klaus) wrote:
>>
>> I have seen reproducible builds being discussed here, but what is the
>> position on inter c-lib and OS reproducible builds?
>
>
> I think we
This adds code to the backend rtx_costs function in order to model the
costs of a load/store on condition.
Bootstrapped and regression tested on s390x.
gcc/ChangeLog:
2017-07-12 Andreas Krebbel
* config/s390/s390.c (s390_rtx_costs): Return proper costs
The backend splitter splitting a 3 operand load on condition into 2 is
wrong. The S/390 load on condition instruction might trap on the
memory operand even if the condition is false. So if the first load
on condition overwrites a register used as part of the memory address
of the second the
On 07/12/2017 05:07 AM, Klaus Kruse Pedersen (Klaus) wrote:
I have seen reproducible builds being discussed here, but what is the
position on inter c-lib and OS reproducible builds?
I think we consider unstable sort problems bugs and have fixed them in
the past. Bugzilla search turned up
On 12 July 2017 at 12:15, Jonathan Wakely wrote:
> On 12/07/17 09:46 +0200, Christophe Lyon wrote:
>>
>> On 11 July 2017 at 14:39, Jonathan Wakely wrote:
>>>
>>> On 11/07/17 12:53 +0100, Jonathan Wakely wrote:
On 21/04/17 15:54 +0100,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81400
--- Comment #3 from Chris Severance ---
Unless there's a security reason 0 should never be used as a canary value.
Errant \0 should be caught 100% of the time. When I built malloc canaries for
NPPTextFX I expressly avoided \0.
ptrace SETREGS and GETREGS were never supported on S/390. The macros
were accidentally defined in the Glibc header though. A recent Glibc
change removed them breaking libgo build on S/390.
This patch changes the ptrace calls to use PEEKUSR_AREA/POKEUSR_AREA to
access the register sets. That's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81069
--- Comment #5 from Tom de Vries ---
Created attachment 41733
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41733=edit
tentative patch, starts neutering alap in nvptx_single
> But in this case, we're extending the sese region being
On 07/11/2017 11:50 PM, sa...@hederstierna.com wrote:
Hi
Reading about macro pitfalls and eg duplication side-effects
https://gcc.gnu.org/onlinedocs/cpp/Macro-Pitfalls.html#Macro-Pitfalls
would it be possible to let the preprocessor generate warnings for any of these
pitfalls?
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81414
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81414
Bug ID: 81414
Summary: ICE in fma steering on AArch64/cortex-a57
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Hi
Your email (gcc-bugs@gcc.gnu.org) was used as the destination of the transfer.
The Transfer should appear in 3 days.
Access key is DfgpU7FRo. You need to enter it to be able to view the attached
file.
Ester Hileman
e55b_Ester Hileman.docx
Description: Attached file: e55b_Ester
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81407
Georg-Johann Lay changed:
What|Removed |Added
Target Milestone|--- |8.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81073
--- Comment #12 from Georg-Johann Lay ---
Thanks, (In reply to Jason Merrill from comment #9)
> Created attachment 41711 [details]
> patch to error on progmem with dynamic init
>
> Does this do what you had in mind?
Hi, thanks. Used to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81407
--- Comment #2 from Georg-Johann Lay ---
Author: gjl
Date: Wed Jul 12 13:58:34 2017
New Revision: 250151
URL: https://gcc.gnu.org/viewcvs?rev=250151=gcc=rev
Log:
PR target/81407
* config/avr/avr.c (avr_encode_section_info)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81407
Georg-Johann Lay changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81412
--- Comment #2 from Huang Zhibin ---
Bug 65757 Status: UNCONFIRMED.
How to fix this Bug?
1 - 100 of 160 matches
Mail list logo