On Fri, Oct 25, 2019 at 1:09 AM Gary Oblock wrote:
>
> I'm wondering if the code in tree-ssa-structalias.c can be invoked in
> a whole program mode? There are some comments in there about
> it not playing well with WHOPR and WPA (not that I intend to use
> that way.) Ironically, in the literature
Hi,
I am trying to track down a code bloat issue and am stuck becauce I do
not understand IRA's cose model.
The test case is as simple as it gets:
float func (float);
float call (float f)
{
return func (f);
}
IRA dump shows the following insns:
(insn 14 4 2 2 (set (reg:SF 44)
On 19/09/2019 18:04, Paul Koning wrote:
On Sep 17, 2019, at 8:02 AM, Richard Earnshaw (lists)
wrote:
...
So in summary my proposed timetable would be:
Monday 16th December 2019 - cut off date for picking which git conversion to use
Tuesday 31st December 2019 - SVN repo becomes read-only a
On 19/09/2019 15:42, Damian Rouson wrote:
On Thu, Sep 19, 2019 at 5:04 AM Janne Blomqvist
wrote:
One thing that's unclear to me is how should I actually make my stuff
appear in the public repo? Say I want to work on some particular
thing:
This is essentially a git workflow question. A sim
On 10/25/19 8:10 AM, Richard Earnshaw (lists) wrote:
> On 19/09/2019 15:42, Damian Rouson wrote:
>> On Thu, Sep 19, 2019 at 5:04 AM Janne Blomqvist
>>
>> wrote:
>>
>>>
>>> One thing that's unclear to me is how should I actually make my stuff
>>> appear in the public repo? Say I want to work on som
> From: David Malcolm
> Sent: Thursday, October 24, 2019 11:18 PM
> On Thu, 2019-10-24 at 20:50 +, Andrew Dean via gcc wrote:
> Thanks for your email, it looks interesting. Is your code somewhere we can
> see
> it?
It can be -- what is the preferred way to share the code? Though to be honest
Snapshot gcc-8-20191025 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/8-20191025/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-8
[Andrew]
| > GCC has some rather unique requirements, in that we support a great many
| > build configurations, some of which are rather primitive - for example,
| > requiring just C++98 with exceptions disabled, in that we want to be able to
| be
| > bootstrappable on relatively "ancient" configu
