Joseph Myers :
> On Thu, 21 Dec 2017, Eric S. Raymond wrote:
>
> > Jeff Law :
> > > I think we've routinely made the ChangeLog date the commit date.
> >
> > Ah, so you modify patches as they come in?
>
> Yes. It's explicitly documented at
> https://gcc.gnu.org/svnwrite.html#checkin - "Use the
On Thu, 21 Dec 2017, Eric S. Raymond wrote:
> Jeff Law :
> > I think we've routinely made the ChangeLog date the commit date.
>
> Ah, so you modify patches as they come in?
Yes. It's explicitly documented at
https://gcc.gnu.org/svnwrite.html#checkin - "Use the current date/time for
the Change
Jeff Law :
> On 12/21/2017 04:13 PM, Eric S. Raymond wrote:
> > Jeff Law :
> >> I think we've routinely made the ChangeLog date the commit date.
> >
> > Ah, so you modify patches as they come in?
> Yes we routinely twiddle the ChangeLog dates. In fact we tried to
> discourage folks from including
On 12/21/2017 04:13 PM, Eric S. Raymond wrote:
> Jeff Law :
>> I think we've routinely made the ChangeLog date the commit date.
>
> Ah, so you modify patches as they come in?
Yes we routinely twiddle the ChangeLog dates. In fact we tried to
discourage folks from including the date/author line in
Jeff Law :
> I think we've routinely made the ChangeLog date the commit date.
Ah, so you modify patches as they come in?
I guess I'd better add that policy switch.
--
http://www.catb.org/~esr/";>Eric S. Raymond
My work is funded by the Internet Civil Engineering Institute: https
On 12/21/2017 03:55 PM, Eric S. Raymond wrote:
> Jason Merrill :
>> YMD in the ChangeLog is typically commit date rather than authorship
>> date anyway, so (i) and (iii) shouldn't differ much at all, and (i)
>> seems simpler.
>
> I have not generally observed this to be true. Maybe it's a GCC-loca
Jason Merrill :
> YMD in the ChangeLog is typically commit date rather than authorship
> date anyway, so (i) and (iii) shouldn't differ much at all, and (i)
> seems simpler.
I have not generally observed this to be true. Maybe it's a GCC-local thing?
When I was an active Emacs contributor but did
On Thu, Dec 21, 2017 at 4:19 PM, Eric S. Raymond wrote:
> The 'changelogs' command of reposugeon attempts to fill in author
> attributions (author and authorship date) by mining Changelogs. It
> makes use of the fact that changesets often contain a change band for
> a Changelog and that change ba
Snapshot gcc-7-20171221 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20171221/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7
The 'changelogs' command of reposugeon attempts to fill in author
attributions (author and authorship date) by mining Changelogs. It
makes use of the fact that changesets often contain a change band for
a Changelog and that change band normally contains or can be referred
to exactly one attributio
I wrote:
>I have implemented the ability for an email address to be declared as
>Lan alias in an author map file. When this is done, that alias will be
>recognized
>in ChangeLog attributions and mapped back to the base address for
>which it is an alias when filling inm Author attributions. Howev
I have implemented the ability for an email address to be declared as
an alias in an author map file. When this is done, that alias will be
recognized
in ChangeLog attributions and mapped back to the base address for
which it is an alias when filling inm Author attributions. However,
the timezon
Hi Bruce,
Thanks for your sharing!
I am porting GlobalISel to RISCV target[1], the highest priority in the
TODO list[2], welcome to contribute to lowRISC, if fixed all the issues,
then I could try to implement RegAllocGraphColoring in HEA and write
great Machine Schedulers.
[1] https://gith
On 12/21/2017 07:52 AM, Stephan Bergmann wrote:
Thinking a bit more about it, I think that's rather a bug in GCC, right?
~ cat test72.cc
#include
#include
void f1();
void f2() noexcept;
int main() { std::cout << (typeid(f1) == typeid(f2)) << '\n'; }
~ g++ -std=c++17 test72.cc
~ ./a.out
1
s
> It's not clear to my why you want this level of detail -- curiosity?
I need to enable this feature on open64.
Thank you all for your great infos.
--
Best Regards,
Yu Rong Tan
So, both AVR and RISC-V are fairly register-rich with usually 32. RV32E
only has 16, but that's still a lot better than i386. If you use a lot of
16 bit integers then AVR also only has effectively 16 registers (or a more
with a mix of 8 and 16 bit variables). 32 bit integers should be rare in
AVR c
16 matches
Mail list logo
