[ was: Re: [PATCH, PR71602] Give error for invalid va_list argument to
va_arg ]
On 23/06/16 23:21, Jason Merrill wrote:
On Thu, Jun 23, 2016 at 1:27 PM, Tom de Vries wrote:
Hi,
this patch fixes PR71602, a 6/7 regression.
Consider this test-case:>> The patch fixes the ICE by making the valid
Hi,
this patch fixes an assert in build_va_arg. Instead of testing for
pointer equality, we use the same test as is used in
std_canonical_va_list_type.
Bootstrapped and reg-tested on x86_64.
OK for trunk?
Thanks,
- Tom
Fix assert in build_va_arg, case 2b
2016-08-22 Tom de Vries
* c-co
Hi,
at the start of build_va_arg, we error out if there's an invalid va_list
argument.
Therefore, the following checks on va_list type are not user errors, but
internal errors.
This patch changes the user errors into internal errors.
Bootstrapped and reg-tested on x86_64.
OK for trunk?
T
Hi,
I.
Consider test-case:
...
struct A {};
void
foo (void)
{
__builtin_va_arg (0, A);
}
...
Compiling this with g++ gives the error:
...
error: first argument to ‘va_arg’ not of type ‘va_list’
...
II.
Now we add ++ in front of the expression, and get:
...
struct A {};
void
foo (void)
{
On 08/23/2016 04:15 PM, Trevor Saunders wrote:
I've certainly been tempted to take a stab at at least replacing the
expect stuff with something else, it drives me kind of crazy to see how
much testsuite time is spent running expect. Even if we can't do all of
it, the vast majority is just run t
This patch broke bootstrap on AIX. Stage1 GCC is miscompiled.
Please revert this patch.
- David
On 8/23/16, David Malcolm wrote:
> Currently our diagnostics subsystem can emit fix-it hints
> suggesting edits the user can make to their code to fix warnings/errors,
> but currently the user must make these edits manually [1].
>
> The following patch kit adds two command-line options with which
On Wed, Aug 24, 2016 at 10:14:29AM +0930, Alan Modra wrote:
> Given a hidden visibility function declaration, the toolchain can say
> that the function is local to the module. This generally means that a
> call to the function can be direct, ie. doesn't need to go via the PLT
> even in a shared li
gcc/ChangeLog:
* Makefile.in (OBJS-libcommon): Add edit-context.o.
* diagnostic-color.c (color_dict): Add "diff-filename",
"diff-hunk", "diff-delete", and "diff-insert".
(parse_gcc_colors): Update default value of GCC_COLORS in comment
to reflect above change
Currently our diagnostics subsystem can emit fix-it hints
suggesting edits the user can make to their code to fix warnings/errors,
but currently the user must make these edits manually [1].
The following patch kit adds two command-line options with which
we can make the changes on behalf of the us
This patch uses the edit_context machinery to provide two new options:
-fdiagnostics-generate-patch
-fdiagnostics-apply-fixits
If either is set, an edit_context is created for global_dc, and any
fix-it hints emitted by diagnostics are added to the edit_context.
-fdiagnostics-generate-patch w
This patch adds foreach, max and min methods to
class typed_splay_tree, along with the start of a selftest
suite.
gcc/ChangeLog:
* Makefile.in (OBJS): Add typed-splay-tree.o.
* selftest-run-tests.c (selftest::run_tests): Call
typed_splay_tree_c_tests.
* selftest.h (
Split out a new base class for temp_source_file, named_temp_file,
moving the deletion to the base class dtor, so that we can write
out temporary files in other ways in selftests.
gcc/ChangeLog:
* selftest.c (selftest::named_temp_file::named_temp_file): New
ctor.
(selftest::
Given a hidden visibility function declaration, the toolchain can say
that the function is local to the module. This generally means that a
call to the function can be direct, ie. doesn't need to go via the PLT
even in a shared library. However, ifunc breaks this promise. GNU
indirect functions
On Tue, 23 Aug 2016, Tom Tromey wrote:
> > "Pedro" == Pedro Alves writes:
>
> >> ISTM we ought to try and rectify the dependency situation for the build
> >> bits. The haphazard way we've managed dependencies may have made sense
> >> in 1992, but doesn't today...
> >> Jeff
>
> Pedro> I can
The OpenACC runtime, specifically GOACC_parallel_keyed, is not
respecting the on device offset of subarrays which may arise in present
data clauses. This is a problem when base element of a subarray some
variable specified in such a present data clause does not match the base
element for a subarray
On 23 August 2016 at 22:56, Martin Sebor wrote:
> Attached is the latest patch.
Some suggestions:
--Wno-format-contains-nul -Wno-format-extra-args -Wformat-nonliteral @gol
+-Wno-format-contains-nul -Wno-format-extra-args -Wformat-length=1 @gol
Most options that take levels are documented as:
-
On 8/22/16, Mike Stump wrote:
> On Aug 22, 2016, at 5:02 AM, Eric Gallager wrote:
>>
>> As a rookie programmer considering possibly contributing to GCC in the
>> future once I'm more confident in my abilities, switching to C++11
>> would increase the barrier for me to contribute. I currently real
On 8/23/16, Gerald Pfeifer wrote:
> I could not find a replacement link, and in any case, isn't the plan
> still to remove the Java frontend before the GCC 7 release?
>
>From lurking the mailing lists, it looked like that's what people were
saying, but I never saw any sort of official deprecation
Some observations:
* Does -fprintf-return-value allow for the possibility of snprintf failing
because of a memory allocation failure and so returning -1 when GCC
computed bounds on what it could return if successful?
* It looks like you convert to (signed/unsigned) char for %hh formats,
etc.
On Mon, Jun 20, 2016 at 02:41:21PM +0100, Dominik Vogt wrote:
> Patch:
> https://gcc.gnu.org/ml/gcc-patches/2016-04/msg01587.html
>
> On Wed, Jan 27, 2016 at 10:39:44AM +0100, Dominik Vogt wrote:
> > g++.dg/tls/thread_local-order2.C no longer fail with Glibc-2.18 or
> > newer since this commit:
>
On Tue, Aug 23, 2016 at 09:52:23AM -0600, Jeff Law wrote:
> On 08/23/2016 02:15 AM, Robert Suchanek wrote:
> > Hi,
> >
> > > unfortunately this broke make check-c
> > > RUNTESTFLAGS='vect.exp=*no-vfa-vect-dv-2.c
> > > --target_board=unix\{-m32,-m64\}', causing the check if
> > > vect_aligned_array
On Tue, 23 Aug 2016, Fritz Reese wrote:
> I would be happy to document my new flags (I have added several) in
> upcoming release notes or applicable documents - however I do not know
> where or how.
I tried to summarize how to checkout and contribute to the web pages
at https://gcc.gnu.org/about.h
On Tue, Aug 23, 2016 at 4:53 PM, Gerald Pfeifer wrote:
> On Mon, 15 Aug 2016, Thomas Koenig wrote:
>> @Gerald: Will a gcc-7/changes.html file be generated? If so, we should
>> document this new flag (and others...)
>
> Yes, please! Segher beat me to it today, sorry for the delay, and
> thanks fo
On Tue, 23 Aug 2016, Segher Boessenkool wrote:
> I'm committing the following to wwwdocs as obvious.
Thank you, Segher! That would have been my late evening program for
today, otherwise. ;-)
Gerald
PS. I did commit a simple patch that de-indents lists, see below.
Index: changes.html
=
On Mon, 15 Aug 2016, Thomas Koenig wrote:
> @Gerald: Will a gcc-7/changes.html file be generated? If so, we should
> document this new flag (and others...)
Yes, please! Segher beat me to it today, sorry for the delay, and
thanks for thinking of our release notes.
Let me know if you need any hel
On Tue, Aug 23, 2016 at 12:58 PM, Dominik Vogt wrote:
> On Tue, Aug 23, 2016 at 11:57:01AM -0700, Ian Lance Taylor wrote:
>> The root cause of https://golang.org/issue/16780 is that GCC on s390
>> GNU/Linux does not emit a .file directive. This is because the
>> function s390_asm_file_start does
The attached patch refines the logic used to suggest the format
attribute to filter out functions that use string literals and
constants as formats.
This change has the effect of not suggesting the attribute for
functions like the one below (since the attribute couldn't very
be used with it):
Successfully bootstrapped®rtested on x86_64-pc-linux-gnu.
Committed to trunk as r239711.
libcpp/ChangeLog:
* include/line-map.h (source_range::from_locations): New method.
---
libcpp/include/line-map.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/libcpp/include/line-ma
I think pr77327 is also yours!-(
Dominique
> Le 23 août 2016 à 21:46, Fritz Reese a écrit :
>
> On Tue, Aug 23, 2016 at 12:22 PM, Dominique d'Humières
> wrote:
>>> This above is pretty clearly a typo. The attached patch committed as
>>> obvious r239706.
>> Could you please provide a test faili
On Tue, Aug 23, 2016 at 11:57:01AM -0700, Ian Lance Taylor wrote:
> The root cause of https://golang.org/issue/16780 is that GCC on s390
> GNU/Linux does not emit a .file directive. This is because the
> function s390_asm_file_start does not call default_file_start, unlike
> most other TARGET_ASM_
On Tue, Aug 23, 2016 at 12:22 PM, Dominique d'Humières
wrote:
>> This above is pretty clearly a typo. The attached patch committed as
>> obvious r239706.
> Could you please provide a test failing before r239706 and succeeding after
> it?
>
I will work on that - it seems to be harder to exhibit t
Found another silly typo in my structure/union patch.
With anonymous nested structures, as with unions and maps (which are
inherently anonymous), a static counter is used to give each type
definition a unique name. Due to a typo the counter for anonymous
structures was not static, therefore was si
On Tue, Aug 23, 2016 at 01:19:36PM -0500, Segher Boessenkool wrote:
> I'm committing the following to wwwdocs as obvious. I hope I did
> everything correct, I'm not a big hero with HTML.
It seems I cannot even run the validator properly. Committing this
fix as well, sigh.
Segher
Index: gcc-7
The root cause of https://golang.org/issue/16780 is that GCC on s390
GNU/Linux does not emit a .file directive. This is because the
function s390_asm_file_start does not call default_file_start, unlike
most other TARGET_ASM_FILE_START hooks. This patch should fix the
problem. Since I don't have
On Tue, 2016-08-23 at 13:43 +0200, Gerald Pfeifer wrote:
> I could not find a replacement link, and in any case, isn't the plan
> still to remove the Java frontend before the GCC 7 release?
>
> Applied.
>
FWIW I found the article inside a PDF at:
https://www.redhat.com/en/files/resources/rh-ma
Hi!
I'm committing the following to wwwdocs as obvious. I hope I did
everything correct, I'm not a big hero with HTML.
This is based on gcc-6/changes.html; all content removed, most headings
commented out, only left some in that surely will get used, it is such
a barren page otherwise.
Gerald,
https://golang.org/issue/15738 points out a bug in the Go frontend:
package priorities are mishandled when using 'go test', such that it
is possible for the packages to be initialized in the wrong order.
The basic problem is that the current package priority system is too
simple, and does not suppo
> "Pedro" == Pedro Alves writes:
>> ISTM we ought to try and rectify the dependency situation for the build
>> bits. The haphazard way we've managed dependencies may have made sense
>> in 1992, but doesn't today...
>> Jeff
Pedro> I can't imagine how would anyone disagree. :-) Maybe Tromey
> This above is pretty clearly a typo. The attached patch committed as
> obvious r239706.
Could you please provide a test failing before r239706 and succeeding after it?
TIA
Dominique
On Mon, Aug 22, 2016 at 5:22 PM, Steve Kargl
wrote:
> Fritz,
>
> I was lookng at part of a previous patch that I committed for you.
> In interface.c, one now has
>
> static int
> compare_components (gfc_component *cmp1, gfc_component *cmp2,
> gfc_symbol *derived1, gfc_symbol *derived2)
> {
>
On 23/08/16 11:16 +0100, Jonathan Wakely wrote:
On 16/07/16 14:55 +0200, Daniel Krügler wrote:
Since I made a similar (unintentional) omission recently myself:
Shouldn't you touch std::__debug::array as well? What about other
functions from std::__debug?
Yes, I'll fix those shortly.
Here's t
On 08/23/2016 02:15 AM, Robert Suchanek wrote:
Hi,
unfortunately this broke make check-c
RUNTESTFLAGS='vect.exp=*no-vfa-vect-dv-2.c
--target_board=unix\{-m32,-m64\}', causing the check if
vect_aligned_arrays to be cached between the -m64 and -m32 variants
which is incorrect at least on my machi
On 08/23/2016 04:37 PM, Jeff Law wrote:
> On 08/23/2016 03:19 AM, Pedro Alves wrote:
>> On 08/23/2016 02:55 AM, Patrick Palka wrote:
>>>
>>> Any reason why automatic dependency generation is not used for the
>>> build/*.o objects too?
>>
>> Historic. Tromey had a big patch a long while ago that ma
On 23 August 2016 at 02:56, David Malcolm wrote:
> On Tue, 2016-08-23 at 00:10 +0530, Prasad Ghangal wrote:
>> On 22 August 2016 at 16:55, Trevor Saunders
>> wrote:
>> > On Sun, Aug 21, 2016 at 10:35:17PM +0530, Prasad Ghangal wrote:
>
> [...]
>
>> > @@ -228,6 +228,12 @@ struct GTY(()) function {
Adhemerval Zanella writes:
> On 08/08/2016 07:58, Jiong Wang wrote:
>>
>> Adhemerval Zanella writes:
>>
>
> Below it the last iteration patch, however I now seeing some similar issue
> s390 hit when building libgo:
>
> ../../../gcc-git/libgo/go/syscall/socket_linux.go:90:1: error: flow control
On 08/23/2016 03:19 AM, Pedro Alves wrote:
On 08/23/2016 02:55 AM, Patrick Palka wrote:
Any reason why automatic dependency generation is not used for the
build/*.o objects too?
Historic. Tromey had a big patch a long while ago that made
everything be covered by auto dependencies. That turn
On 08/19/2016 06:37 PM, David Malcolm wrote:
More enabling work for some new selftests I'm working on.
Successfully bootstrapped®rtested on x86_64-pc-linux-gnu.
OK for trunk?
gcc/ChangeLog:
* selftest.c (selftest::assert_str_contains): New function.
(selftest::test_assertions):
On 08/23/2016 07:59 AM, David Malcolm wrote:
On Mon, 2016-08-22 at 21:25 -0600, Martin Sebor wrote:
Beyond that, the range normally works fine, except when macros
are involved like they are in my tests. You can see the effect
in the range.out file. (This works without your patch but it
could v
On Tue, Aug 23, 2016 at 09:46:50AM +0200, Richard Biener wrote:
> On Mon, Aug 22, 2016 at 11:54 PM, Pedro Alves wrote:
> > On 08/22/2016 10:26 PM, David Malcolm wrote:
> >
> >> it has no problems, whereas with the default for gcc 5 and earlier:
> >>
> >> $ gcc -c test.cc -std=gnu++98
> >> test
On 23/08/16 13:50, Christophe Lyon wrote:
Hi,
While working on a larger patch for PR 67591 (ARM v8 Thumb IT blocks
deprecated),
I have noticed that the predicable_short_it attribute for
arm_movqi_insn is incorrect: the values for alternatives 3 and 4
should be swapped.
This is what this small
Hi,
Ping?
Best regards,
Thomas
On 17/08/16 10:55, Thomas Preudhomme wrote:
Ping?
Best regards,
Thomas
On 10/08/16 14:28, Thomas Preudhomme wrote:
Hi,
Mappings (MULTILIB_MATCHES and MULTILIB_REUSE) in ARM aprofile multilib suffer
from a number of issues:
* missing mapping of -mcpu=cortex
ping
Richard Earnshaw wrote:
> OK. But please enhance the comment with some explanation as to WHY
> you've chosen to use just two base pairings rather than separate bases
> for each access size.
OK here is the updated patch which also handles unaligned accesses
which further improves the ben
ping
Richard Earnshaw wrote:
> I see you've added a default argument for your new parameter. I think
> doing that is fine, but I have two comments about how we might use that
> in this case.
>
> Firstly, if this parameter is suitable for having a default value, then
> I think the preceding o
Ping
I noticed it would still be a good idea to add an extra barrier in the epilog
as the
scheduler doesn't appear to handle aliases of frame accesses properly.
This patch simplifies the handling of the EH return value. We force the use of
the
frame pointer so the return location is always at
Tested on Linux-x64.
N.B. I know that the assignment operators have constraints in template
parameters, I want to move them to the return type separately.
N.B2. This fixes the bug for std::optional only; I plan to port the fix
to std::experimental::optional in a separate patch, and then backport
In aarch64_classify_symbol symbols are allowed full-range offsets on
relocations.
This means the offset can use all of the +/-4GB offset, leaving no offset
available
for the symbol itself. This results in relocation overflow and link-time errors
for simple expressions like &global_char + 0x
Corporate webmasters. Sigh.
Applied.
Gerald
Index: projects/prefetch.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/prefetch.html,v
retrieving revision 1.27
diff -u -r1.27 prefetch.html
--- projects/prefetch.html 14 Nov 2
On Mon, 2016-08-22 at 21:25 -0600, Martin Sebor wrote:
> > > Beyond that, the range normally works fine, except when macros
> > > are involved like they are in my tests. You can see the effect
> > > in the range.out file. (This works without your patch but it
> > > could very well be because I di
Hi,
the attached patch fixes PR 77261. The problem is that with the new
PRNG, the random sequence for real(16) and lesser kinds is not the
same. And then on targets that have real(16) but not real(10) the
testcase fails. Fixed by essentially running the tests only when
real(10) is available.
Regt
This fixes move assignment of RB trees to tag dispatch so the branch
that copies nodes doesn't need to be well-formed.
PR libstdc++/77334
* include/bits/stl_tree.h (_Rb_tree::_M_move_assign): New functions.
(_Rb_tree::operator=(_Rb_tree&&)): Dispatch to _M_move_assign.
Hi,
While working on a larger patch for PR 67591 (ARM v8 Thumb IT blocks
deprecated),
I have noticed that the predicable_short_it attribute for
arm_movqi_insn is incorrect: the values for alternatives 3 and 4
should be swapped.
This is what this small patch does.
Validated on several arm* config
On 23/08/16 11:19 +0100, Jonathan Wakely wrote:
As Casey pointed out, our operator- overloads for reverse_iterator and
move_iterator are not conforming. For reverse_iterator the overload
taking a single template argument is not SFINAE friendly, and for
move_iterator it enables some expressions th
I could not find a replacement link, and in any case, isn't the plan
still to remove the Java frontend before the GCC 7 release?
Applied.
Gerald
2016-08-23 Gerald Pfeifer
* news.html: Remove broken reference to online journal article.
Index: java/news.html
==
On 08/23/2016 10:54 AM, Jonathan Wakely wrote:
>> That's being set by prettyprinters.exp and xmethods.exp (so it's GDB's
>> fault! ;-)
:-)
> This seems to work. I'll do some more testing and commit later today.
LGTM.
Though IME, save/restoring globals in a constant source of trouble,
for occa
On 08/23/2016 08:46 AM, Richard Biener wrote:
> On Mon, Aug 22, 2016 at 11:54 PM, Pedro Alves wrote:
>> I believe that only stage 1 is built with -std=gnu++98 forced, and also
>> stage 1 is built without -Werror, so I think you'd need to start with a
>> compiler that predates support for that con
On 23/08/16 10:04 +0100, Jonathan Wakely wrote:
On 23/08/16 10:45 +0200, Rainer Orth wrote:
Btw., there's one last -pthreads reference left in
libstdc++-v3/doc/xml/manual/using.xml. Perhaps this should go, too.
Ah thanks, I'll update that.
Committed to trunk.
commit d55f8fa4148803c253aafa0
These tests only need to be preprocessed not compiled.
* testsuite/experimental/feat-cxx14.cc: Only preprocess, not compile.
* testsuite/experimental/feat-lib-fund.cc: Likewise.
Tested powerpc64le-linux, committed to trunk.
commit 8ac566ed5dd7b70bc253008d89d569f2dd4dcc33
Author:
As Casey pointed out, our operator- overloads for reverse_iterator and
move_iterator are not conforming. For reverse_iterator the overload
taking a single template argument is not SFINAE friendly, and for
move_iterator it enables some expressions that aren't supposed to be
valid.
This removes the
On 16/07/16 14:55 +0200, Daniel Krügler wrote:
2016-07-16 1:09 GMT+02:00 Jonathan Wakely :
This patch implements http://wg21.link/p0031 which adds constexpr to
most operations on std::reverse_iterator, std::move_iterator,
std::array, as well as std::advance, std::distance, and the
range-access f
On Mon, 22 Aug 2016, Jonathan Wakely wrote:
> So I guess I have no real objection to removing the libstdc++ page.
Based on this, I applied the patch I had posted.
If any of you notices anything to improve upon, let me know and I'll
be happy to work on it.
Gerald
On 23/08/16 09:07 +0100, Jonathan Wakely wrote:
On 22/08/16 21:16 +0100, Pedro Alves wrote:
On 08/22/2016 03:40 PM, Jonathan Wakely wrote:
What's going on?!
Have I fundamentally misunderstood something about how RUNTESTFLAGS or
effective-target keywords work?
Here's a wild guess.
In gdb's
On 23/08/16 11:19 +0200, Rainer Orth wrote:
Hi Jonathan,
The next step would be to replace the explict target list with an
effective-target keyword ;-)
Yes, I've started doing that in a local branch, so we'd use something
like:
{ dg-do run { target libstdc++-threads-supported } }
{ dg-add-op
> gcc/ChangeLog
>
> * explow.c (get_dynamic_stack_size): Take known alignment of stack
> pointer + STACK_DYNAMIC_OFFSET into account when calculating the size
> needed.
> Correct a typo in a comment.
Applied. Thanks!
-Andreas-
> gcc/testsuite/ChangeLog
>
> * gcc.target/s390/insv-1.c: Fix test when running with -m31.
Applied. Thanks!
-Andreas-
On 08/23/2016 02:55 AM, Patrick Palka wrote:
>
> Any reason why automatic dependency generation is not used for the
> build/*.o objects too?
Historic. Tromey had a big patch a long while ago that made
everything be covered by auto dependencies. That turned out to
trickle some GNU make bug and
Hi Jonathan,
>>The next step would be to replace the explict target list with an
>>effective-target keyword ;-)
>
> Yes, I've started doing that in a local branch, so we'd use something
> like:
>
> { dg-do run { target libstdc++-threads-supported } }
> { dg-add-options libstdc++-threads-flags }
>
> gcc/testsuite/ChangeLog
>
> * gcc.target/s390/zvector/vec-genmask-1.c: Improve result verification.
Applies. Thanks!
-Andreas-
On 23/08/16 10:45 +0200, Rainer Orth wrote:
Hi Jonathan,
It's been several years now that Solaris supported -pthread as well as
-pthreads, so there's no need to have separate dg-options directives
for Solaris.
This patch removes all the lines:
// { dg-options "... -pthreads" { target *-*-sola
> gcc/ChangeLog
>
> * config/s390/s390.md ("*andc_split"): New splitter for and with
> complement.
> gcc/testsuite/ChangeLog
>
> * gcc.target/s390/md/andc-splitter-1.c: New test case.
> * gcc.target/s390/md/andc-splitter-2.c: Likewise.
Applied. Thanks!
-Andreas-
On Mon, 22 Aug 2016, Dominique d'Humières wrote:
> This patch causes:
>
> FAIL: gfortran.dg/vect/pr69466.f90 -O (internal compiler error)
> FAIL: gfortran.dg/vect/pr69466.f90 -O (test for excess errors)
> with -m32.
>
> [Book15] f90/bug% gfc
> /opt/gcc/_clean/gcc/testsuite/gfortran.dg/vec
Hi Jonathan,
> It's been several years now that Solaris supported -pthread as well as
> -pthreads, so there's no need to have separate dg-options directives
> for Solaris.
>
> This patch removes all the lines:
>
> // { dg-options "... -pthreads" { target *-*-solaris* } }
>
> And adds *-*-solaris*
Hi,
> unfortunately this broke make check-c
> RUNTESTFLAGS='vect.exp=*no-vfa-vect-dv-2.c
> --target_board=unix\{-m32,-m64\}', causing the check if
> vect_aligned_arrays to be cached between the -m64 and -m32 variants
> which is incorrect at least on my machine if you actually run that test
> for -
On Mon, Aug 22, 2016 at 11:54 PM, Pedro Alves wrote:
> On 08/22/2016 10:26 PM, David Malcolm wrote:
>
>> it has no problems, whereas with the default for gcc 5 and earlier:
>>
>> $ gcc -c test.cc -std=gnu++98
>> test.cc:3:15: warning: non-static data member initializers only
>> available with
On Mon, Aug 22, 2016 at 9:16 PM, H.J. Lu wrote:
> On Thu, Aug 11, 2016 at 1:38 PM, H.J. Lu wrote:
>> alignment_for_piecewise_move is called only with MOVE_MAX_PIECES or
>> STORE_MAX_PIECES, which are the number of bytes at a time that we
>> can move or store efficiently. We should call mode_for_
The link redirected to the Alamden site now, but I found a current
address for the journal.
Applied.
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.252
diff -u -r1.252 reading
gah, this
+ return true;
+ if (TREE_CODE (t1) != SSA_NAME)
should of course be like this
+ if (TREE_CODE (t1) != SSA_NAME)
+ return true;
in the last patch.
87 matches
Mail list logo
