punges the hooks directory.
This appears to be missing some contributors whose usernames I recognise
(starting with me :-) )...
jgreenhalgh = James Greenhalgh (e.g. revision
227028)
ktkachov = Kyrylo Tkachov (e.g. r227012 )
jiwang = Jiong Wang (e.g. r227220 )
renlin = Renlin Li
On Fri, Sep 11, 2015 at 04:31:37PM +0100, Nikolai Bozhenov wrote:
> Hi!
>
> Recently I got somewhat confused by Cortex-A57 pipeline description in
> GCC and
> I would be grateful if you could help me understand a few unclear points.
Sure,
> Particularly I am interested in how memory operations
On Wed, Jan 13, 2016 at 02:17:16PM +0100, Matthias Klose wrote:
> Here are some first results from a distro test rebuild using GCC 6.
> A snapshot of the current Ubuntu development series was taken on
> 20151218 for all architectures (amd64, arm64, armhf, i386/i686,
> powerpc, ppc64el, s390x), and
On Thu, Jan 14, 2016 at 05:15:29PM +, James Greenhalgh wrote:
> On Wed, Jan 13, 2016 at 02:17:16PM +0100, Matthias Klose wrote:
> > Here are some first results from a distro test rebuild using GCC 6.
> > A snapshot of the current Ubuntu development series was taken on
>
On Fri, Jan 15, 2016 at 05:52:49PM +, James Greenhalgh wrote:
>
> libbpp-qt_2.1.0-1ubuntu2
>
> [ ICE: Looks like: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68068
> but reproduces on current trunk. Testcase reducer is in progress. ]
This turned out to be http
On Mon, Jun 20, 2016 at 08:01:24PM +0200, Michael Matz wrote:
> You see, the experiment shows that there's a gazillion uses of basic asms
> out there.
I applied the proposed patch and built myself an allyesconfig AArch64 linux
kernel, the results were not pretty...
make | grep "warning: Depre
On Thu, Aug 04, 2016 at 09:12:36PM +0100, Manuel López-Ibáñez wrote:
> On 04/08/16 15:49, Thomas Schwinge wrote:
> >I suppose, if I weren't paid for paid for this, I would have run away
> >long ago, and would have looked for another project to contribute to.
> >:-(
>
> You are a *paid* developer f
On Fri, Aug 05, 2016 at 04:38:30PM +0100, Manuel López-Ibáñez wrote:
> I think those conclusions are debatable:
I won't respond to all your points (I'm busy this evening), but I can
regenerate my table with some of your suggestions.
> * GCC has also grown over the years, there is a lot more cod
On Fri, Jul 11, 2014 at 07:52:06PM +0100, Franzi Edo. wrote:
> Hi All,
> Thank you for your suggestions.
> Unfortunately, no way!
>
> 4. I can generate my cross compiler based on the "gcc 4.8.3” without problem
> (using both the apple-gcc4.2 or the XCode llvm) So, what has changed of
> fundamental
On Thu, Apr 02, 2015 at 04:20:06AM +0100, Ekanathan, Saravanan wrote:
> (I had sent this mail to gcc-help a week ago. Not sure, all GCC developers
> are subscribed to gcc-help, so re-sending to GCC development mailing list)
>
> Hi,
>
> This looks like a missed vectorization opportunity for one of t
On Mon, Apr 27, 2015 at 09:37:36AM +0100, Richard Biener wrote:
> On Sun, Apr 26, 2015 at 9:56 AM, Honggyu Kim wrote:
> > Hi all,
> >
> > I would like to know about the stages of development plan so I checked the
> > following article:
> > https://gcc.gnu.org/develop.html
[Just Bike-shedding...]
ons to
the AArch64 port over the past two years.
Kyrill Tkachov, Richard Earnshaw, Richard Sandiford and Marcus Shawcroft
make for a great team of maintainers - I fully expect the AArch64 to
continue to thrive under their watch.
Best Regards,
James
2019-11-19 James Greenhalgh
* M
On Wed, Mar 15, 2017 at 09:50:18AM +, Sekhar, Ashwin wrote:
> Hi GCC Team, Aarch64 Maintainers,
>
>
> The rules in Vector Function Application Binary Interface Specification for
> OpenMP
> (https://sourceware.org/glibc/wiki/libmvec?action=AttachFile&do=view&target=VectorABI.txt)
> is used in
On Tue, Aug 01, 2017 at 11:12:12AM -0400, Eric Gallager wrote:
> On 8/1/17, Jakub Jelinek wrote:
> > On Tue, Aug 01, 2017 at 07:08:41AM -0400, Eric Gallager wrote:
> >> > Heh. I suspect -Os would benefit from a separate compilation pipeline
> >> > such as -Og. Nowadays the early optimization pip
On Wed, Aug 02, 2017 at 12:56:58PM -0700, Richard Henderson wrote:
> On 08/02/2017 12:34 PM, Richard Earnshaw wrote:
> > I'm not sure if that's a good or a bad thing. Currently the mid-end
> > depends on some rtx constructs having sensible costs even if there's no
> > rtl pattern to match them (II
On Sat, Sep 09, 2017 at 12:44:14PM +0100, Ramana Radhakrishnan wrote:
> I'm pleased to announce that the steering committee has appointed
>
> - James Greenhalgh as a full maintainer for the AArch64 port
>
> and
>
> - Kyrylo Tkachov as a full maintainer for the ARM po
On Wed, Dec 20, 2017 at 10:02:45AM +, Paulo Matos wrote:
>
>
> On 20/12/17 10:51, Christophe Lyon wrote:
> >
> > The recent fix changed the Makefile and configure script in libatomic.
> > I guess that if your incremental builds does not run configure, it's
> > still using old Makefiles, and
On Fri, Jun 08, 2018 at 04:01:14PM -0500, Steve Ellcey wrote:
> I have a question about the Aarch64 simd instructions and builtins.
>
> I want to unpack a __Float32x4 (V4SF) variable into two __Float64x2
> variables. I can get the upper part with:
>
> __Float64x2_t a = __builtin_aarch64_vec_unpa
On Fri, Nov 22, 2013 at 11:03:22AM +, Bingfeng Mei wrote:
> Well, in your modified example, it is still due to jump threading that produce
> code of bad control flow that cannot be if-converted and vectorized, though in
> tree-vrp pass this time.
>
> Try this
> ~/install-4.8/bin/gcc vect-ifc
On Thu, Feb 27, 2014 at 11:07:21AM +, Andrew Haley wrote:
> Over the years there has been a great deal of traffic on these lists
> caused by misunderstandings of GCC's inline assembler. That's partly
> because it's inherently tricky, but the existing documentation needs
> to be improved.
>
>
20 matches
Mail list logo
