On December 14, 2019 6:28:48 AM GMT+01:00, Andrew Pinski
wrote:
>On Mon, May 9, 2016 at 2:32 AM Richard Biener
>wrote:
>>
>>
>> I am testing the following followup to my BIT_FIELD_REF
>simplification
>> changes which resolve issues when applying to memory BIT_FIELD_REFs.
>>
>> Bootstrap and regt
On Mon, May 9, 2016 at 2:32 AM Richard Biener wrote:
>
>
> I am testing the following followup to my BIT_FIELD_REF simplification
> changes which resolve issues when applying to memory BIT_FIELD_REFs.
>
> Bootstrap and regtest running on x86_64-unknown-linux-gnu.
My question is not directly relat
Am 2019-12-14 04:03, schrieb Andrew Pinski:
On Fri, Dec 13, 2019 at 6:56 PM Stefan Franke wrote:
Am 2019-12-13 21:59, schrieb Segher Boessenkool:
> On Fri, Dec 13, 2019 at 08:55:15PM +0100, Stefan Franke wrote:
>> Am 2019-12-13 18:58, schrieb Segher Boessenkool:
>> >On Fri, Dec 13, 2019 at 05:
On Fri, Dec 13, 2019 at 6:56 PM Stefan Franke wrote:
>
> Am 2019-12-13 21:59, schrieb Segher Boessenkool:
> > On Fri, Dec 13, 2019 at 08:55:15PM +0100, Stefan Franke wrote:
> >> Am 2019-12-13 18:58, schrieb Segher Boessenkool:
> >> >On Fri, Dec 13, 2019 at 05:25:41PM +0100, Stefan Franke wrote:
>
Am 2019-12-13 21:59, schrieb Segher Boessenkool:
On Fri, Dec 13, 2019 at 08:55:15PM +0100, Stefan Franke wrote:
Am 2019-12-13 18:58, schrieb Segher Boessenkool:
>On Fri, Dec 13, 2019 at 05:25:41PM +0100, Stefan Franke wrote:
>>Why? If you are using a cc register plus your architecture as many
>>
After more testing by Jeff's buildbot and correcting the problems
it exposed I have committed the attached patch in r279392.
Martin
On 12/11/19 4:23 PM, Martin Sebor wrote:
Jeff's buildbot exposed a bug in the patch that caused false
positives in cases involving negative offsets into destinatio
On Fri, 13 Dec 2019 16:25:25 +0100
Thomas Schwinge wrote:
> Hi Julian!
>
> On 2019-10-29T12:15:01+, Julian Brown
> wrote:
> > static int
> > -find_pointer (int pos, size_t mapnum, unsigned short *kinds)
> > +find_group_last (int pos, size_t mapnum, unsigned short *kinds)
> > {
> > - if (
On Fri, 13 Dec 2019 15:13:53 +0100
Thomas Schwinge wrote:
> Hi!
>
> Julian, Tobias, regarding the following OpenACC 'exit data' 'finalize'
> handling:
>
> On 2018-05-25T13:01:58-0700, Cesar Philippidis
> wrote:
> > --- a/gcc/gimplify.c
> > +++ b/gcc/gimplify.c
>
> > @@ -10859,6 +10849,53 @@
On 12/13/19 3:20 PM, Marek Polacek wrote:
On Thu, Dec 12, 2019 at 02:38:29PM -0500, Jason Merrill wrote:
On 12/11/19 5:50 PM, Marek Polacek wrote:
On Fri, Nov 22, 2019 at 04:11:53PM -0500, Jason Merrill wrote:
On 11/8/19 4:24 PM, Marek Polacek wrote:
2) [class.cdtor] says that when a dynami
I've updated the gccgo branch to revision 279380 of trunk.
Ian
Here is a patch to fix prettyprinters.exp failures in normal and debug
modes.
In 80276.cc I replicate the #define with comment from other tests even
if it isn't true that cxx11 abi string isn't supported. It's just that
it doesn't appear as 'std::string', the aliasing doesn't work.
I still h
On Darwin10 it's possible to make a 32b PPC build using the
'Rosetta' emulator. However, these builds need to make use of
Darwin9 crts (for exes and dylibs). This adds the change to
cater for dylibs.
tested on a powerpc-darwin10 native and a powerpc-darwin10
cross from x86_64-darwin16.
applied
On Fri, Dec 13, 2019 at 08:55:15PM +0100, Stefan Franke wrote:
> Am 2019-12-13 18:58, schrieb Segher Boessenkool:
> >On Fri, Dec 13, 2019 at 05:25:41PM +0100, Stefan Franke wrote:
> >>Why? If you are using a cc register plus your architecture as many
> >>instructions which may clobber that cc regis
On Thu, Dec 12, 2019 at 02:38:29PM -0500, Jason Merrill wrote:
> On 12/11/19 5:50 PM, Marek Polacek wrote:
> > On Fri, Nov 22, 2019 at 04:11:53PM -0500, Jason Merrill wrote:
> > > On 11/8/19 4:24 PM, Marek Polacek wrote:
>
> > > > 2) [class.cdtor] says that when a dynamic_cast is used in a constru
This patch to libbacktrace adds DWARF 5 support. I tested this with
GCC 8, GCC tip, and clang 8, using the -gdwarf-5 option. Bootstrapped
and ran libbacktrace and libgo tests on x86_64-pc-linux-gnu.
Committed to mainline.
Ian
2019-12-13 Ian Lance Taylor
Add DWARF 5 support.
* dwarf.c (struc
Am 2019-12-13 18:58, schrieb Segher Boessenkool:
Hi!
On Fri, Dec 13, 2019 at 05:25:41PM +0100, Stefan Franke wrote:
I suggest this patch to allow architectures do substitute cc0_rtx with
a
generated cc register.
Why? If you are using a cc register plus your architecture as many
instructions w
On Fri, 2019-12-13 at 19:27 +0100, Jakub Jelinek wrote:
> On Fri, Dec 13, 2019 at 01:11:05PM -0500, David Malcolm wrote:
> > gcc/ChangeLog:
> > * builtins.def (BUILT_IN_ANALYZER_BREAK): New builtin.
> > (BUILT_IN_ANALYZER_DUMP): New builtin.
> > (BUILT_IN_ANALYZER_DUMP_EXPLODED_NODES):
On Fri, Dec 13, 2019 at 01:11:05PM -0500, David Malcolm wrote:
> gcc/ChangeLog:
> * builtins.def (BUILT_IN_ANALYZER_BREAK): New builtin.
> (BUILT_IN_ANALYZER_DUMP): New builtin.
> (BUILT_IN_ANALYZER_DUMP_EXPLODED_NODES): New builtin.
> (BUILT_IN_ANALYZER_DUMP_NUM_HEAP_REGION
New in v4; part of:
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00214.html
with various fixups
gcc/ChangeLog:
* analyzer/sm-signal.cc: New file.
---
gcc/analyzer/sm-signal.cc | 306 ++
1 file changed, 306 insertions(+)
create mode 100644 gcc/analyz
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Use TV_ANALYZER_PLAN rather than an auto_client_timevar.
- Update for new param API.
- Add DISABLE_COPY_AND_ASSIGN (analysis_plan);
This patch adds an analysis_plan class, wh
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
- Rework on_leak vfunc:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02028.html
This patch adds a custom state machine checker intended purely f
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
- Add support for global state:
- https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00217.html
- Rework logging to avoid exploded_graph multiple-inherit
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
- Rework on_leak vfunc:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02028.html
- Rework for changes to is_named_call_p, resolving function point
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
This patch adds classes for tracking the equivalence classes and
constraints that hold at a point on an execution path.
gcc/ChangeLog:
* ana
Changed in v4:
- Moved from gcc/analyzer to gcc, renaming selftests accordingly
- Remove comments
- Replace auto_client_timevar with TV_ANALYZER_SHORTEST_PATHS
This patch adds template classes for directed graphs, their nodes
and edges, and for finding the shortest path through such a g
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
- Add custom events:
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00213.html
- Generalize rewind_info_t to exploded_edge::custom_info_t
https
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
- Rework logging to avoid exploded_graph multiple-inheritance (moving
log_user base to a member)
- Support resolving function pointers:
https://g
This patch adds a "break-on-saved-diagnostic" command to gdbinit.in,
useful for debugging when a diagnostic is queued by the analyzer.
gcc/ChangeLog:
* gdbinit.in (break-on-saved-diagnostic): New command.
---
gcc/gdbinit.in | 10 ++
1 file changed, 10 insertions(+)
diff --git a/g
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
- Use TV_ANALYZER_STATE_PURGE rather than an auto_client_timevar
- Fix .dot output:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02461.html
- Add
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
- Add custom events:
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00213.html
- Add support for global state:
https://gcc.gnu.org/ml/gcc-patch
Changed in v4:
- Remove /// comment lines
- Don't use multiple inheritance, instead adding a log_user member.
- Add more validation, part of:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02517.html
- Generalize rewind_info_t to exploded_edge::custom_info_t
https://gcc.gnu.org/ml/gcc-patche
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
- Rework on_leak vfunc:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02028.html
- Rework for changes to is_named_call_p, resolving function point
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Add call_string::validate, part of:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02517.html
This patch adds call_string, a class for representing the
call stacks at a pr
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
- Add support for more validation, part of:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02517.html
- Rework logging to avoid exploded_graph mult
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
- Rework on_leak vfunc:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02028.html
- Rework for changes to is_named_call_p, resolving function point
Changed in v4:
- Add support for paths for signal-handlers:
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00215.html
- Fix comment
Changed in v3:
- Fixup for rebase (r278634): c-format.c: get_pointer_to_named_type ->
get_named_type
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00530.html
C
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
- Rework on_leak vfunc:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02028.html
- Rework for changes to is_named_call_p, resolving function point
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Capture const state_change_event& in evdesc_state_change:
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00218.html
This patch adds classes used by the analyzer for handli
Changed in v4:
- moved from gcc/analyzer to gcc
gcc/ChangeLog:
* tristate.cc: New file.
* tristate.h: New file.
---
gcc/tristate.cc | 221
gcc/tristate.h | 82 ++
2 files changed, 303 insertions(+)
create mode 100
Changed in v4:
- Rework includes to avoid gcc-plugin.h
- Wrap everything with #if ENABLE_ANALYZER
- Replace auto_client_timevar with TV_ANALYZER_SUPERGRAPH
- Fix .dot output
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02461.html
- Update for move of digraph.h
This patch adds a "supergraph" cla
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
- Add call to make_signal_state_machine:
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00214.html
- Rework on_leak vfunc:
https://gcc.gnu.org/
Changed in v3:
- https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02461.html
- moved from gcc/analyzer to gcc
This patch adds a simple wrapper class to make it easier to
write human-readable .dot files.
gcc/ChangeLog:
* graphviz.cc: New file.
* graphviz.h: New file.
---
gcc/graphviz
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Wrap everything in #if ENABLE_ANALYZER
- Remove /// comment lines
- Update is_named_call_p to support function pointers:
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00178.html
gcc/ChangeLog:
* analyzer
Changed in v4:
- Remove include of gcc-plugin.h
- call run_analyzer_selftests directly, rather than via plugin
registration; wrap the analyzer selftests in #if ENABLE_ANALYZER
- fixup for moves of digraph.cc and tristate.cc from gcc/analyzer to gcc
gcc/ChangeLog:
* analyzer/analyzer-self
This patch adds an ordered_hash_map template, which is similar to
hash_map, but preserves insertion order.
gcc/ChangeLog:
* Makefile.in (OBJS): Add ordered-hash-map-tests.o.
* ordered-hash-map-tests.cc: New file.
* ordered-hash-map.h: New file.
* selftest-run-tests.
Changed in v4:
- wrap with #if ENABLE_ANALYZER
- add DISABLE_COPY_AND_ASSIGN
This patch adds a logging framework to the analyzer which handles
hierarchical messages (showing the nested structure of the calls).
This code is largely based on that in the "jit" subdirectory (with
a few changes). An
Changed in v4:
- Renamed gcc/analyzer/plugin.opt to gcc/analyzer/analyzer.opt
- Change option from -analyzer to -fanalyzer, changed it from
Driver to Common.
- Various commits on 2019-11-12 including r278083 through r278087
reimplemented parameter-handling in terms of options, so that
param
Changed in v4:
- Remove include of gcc-plugin.h, reworking includes accordingly.
- Use TV_ANALYZER rather than TV_NONE for the pass
- Add a gate function to the pass
- Move the check for #if ENABLE_ANALYZER from the driver to the
pass's execute vfunc
- Expose the pass via make_pass_analyzer, rath
Here's an updated version of the patch kit, addressing many issues from
review, and squashing in other changes.
This is v4, and is relative to r279310 (2019-12-12)
Earlier versions:
v3: https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00529.html
v2: https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02024
gcc/ChangeLog:
* builtins.def (BUILT_IN_ANALYZER_BREAK): New builtin.
(BUILT_IN_ANALYZER_DUMP): New builtin.
(BUILT_IN_ANALYZER_DUMP_EXPLODED_NODES): New builtin.
(BUILT_IN_ANALYZER_DUMP_NUM_HEAP_REGIONS): New builtin.
(BUILT_IN_ANALYZER_DUMP_PATH): New built
gcc/ChangeLog:
* Makefile.in (lang_opt_files): Add analyzer.opt.
(ANALYZER_OBJS): New.
(OBJS): Add digraph.o, graphviz.o, tristate.o and ANALYZER_OBJS.
---
gcc/Makefile.in | 32 +++-
1 file changed, 31 insertions(+), 1 deletion(-)
diff --git a/g
This patch adds a configuration option to disable building the analyzer.
It is built by default (but off by default at compile-time).
gcc/ChangeLog:
* configure.ac (--disable-analyzer, ENABLE_ANALYZER): New option.
(gccdepdir): Also create depdir for "analyzer" subdir.
---
gcc/con
Changed in v4:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02026.html
gcc/ChangeLog:
* Makefile.in (TEXI_GCCINT_FILES): Add analyzer.texi.
* doc/analyzer.texi: New file.
* doc/gccint.texi ("Static Analyzer") New menu item.
(analyzer.texi): Include it.
---
gcc/M
gcc/ChangeLog:
* pretty-print.c (pp_write_text_as_html_like_dot_to_stream): New
function.
* pretty-print.h (pp_write_text_as_html_like_dot_to_stream): New decl.
---
gcc/pretty-print.c | 48 ++
gcc/pretty-print.h | 3 +++
2 files
This takes the place of the auto_client_timevar code from v1 of the kit:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg01519.html
gcc/ChangeLog:
* timevar.def (TV_ANALYZER): New timevar.
(TV_ANALYZER_SUPERGRAPH): Likewise.
(TV_ANALYZER_STATE_PURGE): Likewise.
(TV_
Changed in v2:
fixup for json::number -> json::integer_number change (r277284)
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02027.html
This patch adds support for associating a diagnostic with an optional
diagnostic_metadata object, so that plugins can add extra data to their
diagnostics (e
This patch implements -fdiagnostics-nn-line-numbers, a new option
which makes diagnostic_show_locus print "NN" rather than specific
line numbers when printing the left margin.
This is intended purely to make it easier to write certain kinds of
DejaGnu test; various integration tests for diagnostic
Changed in v4:
- Use -fanalyzer rather than --analyzer
- Add -W[no-]analyzer-unsafe-call-within-signal-handler
gcc/ChangeLog:
* doc/invoke.texi ("Static Analyzer Options"): New list and new section.
("Warning Options"): Add static analysis warnings to the list.
(-Wno-analyz
This patch converts various "gimple *" to "const gimple *" and similar
fixes for gimple subclasses, adding is_a_helper for gimple subclasses
to support the const form of as_a, and adding a few "const" overloads
of accessors.
This is enough to make pp_gimple_stmt_1's stmt const.
gcc/ChangeLog:
Changed in v4: added DISABLE_COPY_AND_ASSIGN
This patch adds a class auto_delete_vec, a subclass of auto_vec
that deletes all of its elements on destruction; it's used in many
places later in the kit.
This is a crude way for a vec to "own" the objects it points to
and clean up automatically (ess
gcc/ChangeLog:
* sbitmap.h (auto_sbitmap): Add operator const sbitmap &.
---
gcc/sbitmap.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/gcc/sbitmap.h b/gcc/sbitmap.h
index a33175d26f75..3c5b0a47a004 100644
--- a/gcc/sbitmap.h
+++ b/gcc/sbitmap.h
@@ -295,6 +295,7 @@ public:
/* A
gcc/ChangeLog:
* hash-map-tests.c (selftest::test_map_of_int_to_strings): New
selftest.
(selftest::hash_map_tests_c_tests): Call it.
---
gcc/hash-map-tests.c | 41 +
1 file changed, 41 insertions(+)
diff --git a/gcc/hash-map-tests.c
Hi!
On Fri, Dec 13, 2019 at 05:25:41PM +0100, Stefan Franke wrote:
> I suggest this patch to allow architectures do substitute cc0_rtx with a
> generated cc register.
>
> Why? If you are using a cc register plus your architecture as many
> instructions which may clobber that cc register, some p
This change adjusts the libstdc++ configuration for VxWorks
to set ac_has_nanosleep=yes, which enables the use of nanosleep
from the library.
While this technically depends on the kernel configuration
(INCLUDE_POSIX_TIMERS) this is the normal configuration in all
the environments we have been giv
On 19/11/2019 12:21, Andrew Stubbs wrote:
This patch adds GCN special casing for most of the OpenACC libgomp tests
that require it. It also disables one testcase that explicitly uses CUDA.
The patches aren't all that controversial, should only change the
results on amdgcn, and Tobias already w
On Fri, 2019-12-13 at 09:43 -0700, Martin Sebor wrote:
> On 12/12/19 7:59 PM, David Malcolm wrote:
> > On Wed, 2019-12-04 at 10:36 -0700, Martin Sebor wrote:
> > > On 11/15/19 6:22 PM, David Malcolm wrote:
> > > > This patch adds support for associating a diagnostic with an
> > > > optional
> > > >
Hello,
This change reworks the VxWorks specific os_defines.h internal
lisbstdc++ header to help fix build and runtime failures of various
kinds in environments from 6.4/6.9 to 7 SR640, based on experiments
and observations conducted against real installs of these OSes for
different CPU architectur
On Vxworks 7, includers of stdint.h (which we currently "provide")
need yvals.h to have been included ahead.
Instead of altering the common stdint-gcc.h with unpleasant
vxworks specific bits to do that, we arrange to provide stdint-gcc.h
on its own along with a stdint.h wrapper which preincludes
On 12/12/19 7:59 PM, David Malcolm wrote:
On Wed, 2019-12-04 at 10:36 -0700, Martin Sebor wrote:
On 11/15/19 6:22 PM, David Malcolm wrote:
This patch adds support for associating a diagnostic with an
optional
diagnostic_metadata object, so that plugins can add extra data to
their
diagnostics (e
I've committed this patch to add v64qi and v64hi multiply patterns.
This is slowly working toward full char and short vectorization.
Andrew
Sub-dword vector multiply for amdgcn
2019-12-13 Andrew Stubbs
gcc/
* config/gcn/gcn-valu.md (mulv64si3): Rename to ...
(mul3): ... this, and impleme
Starting from VxWorks 7, the system comes with a Dinkumware
environment which requires the inclusion of "yvals.h" before other
system headers. We provide wrapped versions of a few headers to
accommodate such constraints.
Initially proposed by Jérôme, this helps fix dozens of build issues
whe
Hi there,
I suggest this patch to allow architectures do substitute cc0_rtx with a
generated cc register.
Why? If you are using a cc register plus your architecture as many
instructions which may clobber that cc register, some passes (e.g. gcse)
will reorder the insns. This can lead to the s
This changes introduces an internal API for VxWorks version checks
within runtime files, a prerequisite to a few fixes coming up for libstdc++
builds on more recent versions of the OS.
Tested in accordance with the description in
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00911.html
Committin
The patch by Joel setting up TARGET_C_PREINCLUDE exposed a possibility
to simplify/robustify the compilation commands use for another source in
the t-vxworks Makefile fragment.
We now leverage $(COMPILE) and $(POSTCOMPILE) instead of replicating
them manually for vxworks.c.
Tested in accordance
This patch modifies the C & C++ VxWorks compiler to predefine
the __STDC_ macros verified by gcc.dg/c99-predef-1.c in the testsuite.
We setup a vxworks-predef.h header file which arranges to define
TARGET_C_PREINCLUDE, in a separate config/vxworks
directory where other runtime header files will
This change refines the VxWorks macro definitions configuring
wchar_t to accommodate the VxWorks7 environment, where wchar_t
is now typically a 32bit type.
We also ensure that the definitions for wint_t are always based
on those for wchar_t, so the two remain in sync in environments
where WCHAR_T
This patch simply adds sectioning comments in vx-common.h
and moves the NO_DOLLAR/DOT_IN_LABEL block down, away from the
section now dedicated to SPEC strings.
Goal to improve readability and facilitate future changes to come.
Tested in accordance with the description in
https://gcc.gnu.org/ml/gc
Hi,
while looking into Firefox regression compared to gcc9 I noticed that we
often confuse common target infos when profiles get merged. This patch
adds the missing update bits.
Honza
* ipa-utils.c (ipa_merge_profiles): Improve dumping; merge common
targets.
Index: ipa-utils.c
=
I've committed the attached patch to add extend, zero_extend, and trunc
instructions patterns to, from and between the v64qi and v64hi modes.
The patch adds both normal and the masked "exec" variants of the
patterns, as per the rest of the machine description.
The FP conversions also had to b
On Sat, Dec 14, 2019 at 12:06:36AM +0900, Oleg Endo wrote:
> On Fri, 2019-12-13 at 15:57 +0100, John Paul Adrian Glaubitz wrote:
> > Hello Segher!
Hi :-)
> > > With LRA, sh builds fine (with the combine2 patches). I have no idea
> > > if correct code is generated, but it doesn't ICE anymore.
> >
John Paul Adrian Glaubitz writes:
> Hi!
>
> On 12/13/19 4:06 PM, Oleg Endo wrote:
>>> What are the combine2 patches?
>>
>> See the other thread that I've linked in my message.
>
> I don't see any patch there.
The latest version is: https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00287.html
Origina
On Fri, 2019-12-13 at 16:09 +0100, John Paul Adrian Glaubitz wrote:
> Hi!
>
> On 12/13/19 4:06 PM, Oleg Endo wrote:
> > > What are the combine2 patches?
> >
> > See the other thread that I've linked in my message.
>
> I don't see any patch there.
You'd have to crawl up the discussion or so.
And
Hi Julian!
On 2019-10-29T12:15:01+, Julian Brown wrote:
> On Mon, 21 Oct 2019 16:14:11 +0200
> Thomas Schwinge wrote:
>
>> On 2019-10-03T09:35:04-0700, Julian Brown
>> wrote:
>> > --- a/libgomp/oacc-parallel.c
>> > +++ b/libgomp/oacc-parallel.c
>> > @@ -56,12 +56,29 @@ find_pointer (int pos
Hi!
On 12/13/19 4:06 PM, Oleg Endo wrote:
>> What are the combine2 patches?
>
> See the other thread that I've linked in my message.
I don't see any patch there.
>> And I would support switching SH to LRA as
>> there are a few cases (Debian packages) where GCC fails with an internal
>> compile
On Fri, 2019-12-13 at 05:03 -0600, Segher Boessenkool wrote:
> On Thu, Dec 12, 2019 at 09:32:27AM +, Richard Sandiford wrote:
> > I doubt it will be long before we deprecate
> > all targets that require old reload.)
>
> Do we wait until GCC 12 (to remove old reload completely)? If not, we
> s
On Fri, 2019-12-13 at 15:57 +0100, John Paul Adrian Glaubitz wrote:
> Hello Segher!
>
> > With LRA, sh builds fine (with the combine2 patches). I have no idea
> > if correct code is generated, but it doesn't ICE anymore.
>
> What are the combine2 patches?
See the other thread that I've linked i
Hello Segher!
> With LRA, sh builds fine (with the combine2 patches). I have no idea
> if correct code is generated, but it doesn't ICE anymore.
What are the combine2 patches? And I would support switching SH to LRA as
there are a few cases (Debian packages) where GCC fails with an internal
comp
Hi Julian!
On 2019-12-12T19:01:21+, Julian Brown wrote:
> This is a fix for PR92881, broken out of the larger "reference counting
> overhaul" patch last posted here:
>
> https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02235.html
Thanks!
> The current implementation (potentially with synchrono
As long as one compiles for a single target, the message is unlikely to appear.
However, when compiling for offloading, the modes supported on the target
'host' and on the target 'device' can be different. In particular,
'long double' (when larger than double) and '__float128' might not be
availa
Prior to VxWorks 7, the path where startfiles and core
libraries are located contains CPU architecture specific name
components. This should normally be expressed through a CPU
specific STARTFILE_PREFIX_SPEC for such versions of VxWorks.
This change adds a definition for the PowerPc family, which
On Fri, 2019-12-13 at 08:09 -0600, Segher Boessenkool wrote:
> On Fri, Dec 13, 2019 at 10:06:20PM +0900, Oleg Endo wrote:
> > On Fri, 2019-12-13 at 05:03 -0600, Segher Boessenkool wrote:
> > > On Thu, Dec 12, 2019 at 09:32:27AM +, Richard Sandiford
> > > wrote:
> > > > I doubt it will be long b
Hi!
Julian, Tobias, regarding the following OpenACC 'exit data' 'finalize'
handling:
On 2018-05-25T13:01:58-0700, Cesar Philippidis wrote:
> --- a/gcc/gimplify.c
> +++ b/gcc/gimplify.c
> @@ -10859,6 +10849,53 @@ gimplify_omp_target_update (tree *expr_p, gimple_seq
> *pre_p)
> + else if (TREE
On Fri, Dec 13, 2019 at 01:19:55PM +0100, Richard Biener wrote:
> On December 13, 2019 12:03:30 PM GMT+01:00, Segher Boessenkool
> wrote:
> >On Thu, Dec 12, 2019 at 09:32:27AM +, Richard Sandiford wrote:
> >> I doubt it will be long before we deprecate
> >> all targets that require old reload
On Fri, Dec 13, 2019 at 10:06:20PM +0900, Oleg Endo wrote:
> On Fri, 2019-12-13 at 05:03 -0600, Segher Boessenkool wrote:
> > On Thu, Dec 12, 2019 at 09:32:27AM +, Richard Sandiford wrote:
> > > I doubt it will be long before we deprecate
> > > all targets that require old reload.)
> >
> > Do
This change fixes latent failures actually observed when activating
libstdc++ for VxWorks on aarch46 VxWorks 7 and powerpc VxWorks 6.
The system limits.h is dated on some configurations, so we
provide our own version to expose constants required by more
recent C standards. Our versio
This change improves the GTHREAD_ONCE_INIT initializer
exposed by gthr-vxworks.h to use a more standard syntax
for a zero-initialization, which fixes build failures
observed when activating libstdc++ builds for aarch64-vxworks.
Tested in accordance with the description in
https://gcc.gnu.org/ml/g
This change fixes a typo in a macro name reference, introduced
by mistake during a refactoring.
Tested in accordance with the description in
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00911.html
Committing to mainline.
Olivier
2019-12-13 Olivier Hainque
libgcc/
* con
Hello,
This patch fixes an obvious typo in a macro name used to
guard some definitions used later on in vxcrtstuff.c, leading
to an unexpected mix of symbols in a vxcrtbegin variant and
incorrect behavior for the corresponding mode at run time.
Tested in accordance with the description in
https:/
Richard Biener writes:
>>> The frontend are in charge of specifying the actual argument type and
>>> at that point the target may fix the ABI. The ABI can be recorded in
>>> the calls fntype, either via its TYPE_ARG_TYPES or in more awkward
>>> ways for varargs functions (in full generality that w
Consequently whilst looking at the list I noticed these two were missing.
This OK for trunk?
gcc/ChangeLog:
2019-12-13 Andre Vieira
* doc/sourcebuild.texi (arm_little_endian, arm_nothumb):
Documented existing target checks.
On 13/12/2019 13:05, Andre Vieira (lists) wrote:
Th
1 - 100 of 137 matches
Mail list logo
