Thank you!

2019-03-05 Thread SaapVer
Hi DannyEdupt,

Thank you for contacting us.
We will be in touch with you shortly.

--
This e-mail was sent from a contact form on SaapVer (http://saapver.com/)



Thank you for paying from the Adobe Store. Here are details about your Payment:

2018-03-29 Thread ADOBE via gcc





October 31



















October 31, 2013





















   







Your Payment confirmation





   



 



    Dear g...@gnu.org    



 



    Thank you for paying from the Adobe Store. Here are
details about your Payment:    



 



   











Adobe ID:

g...@gnu.org





Order number:

AD010031934





Payment date:

March 24, 2018,





Products ordered:





Qty Product



1 Adobe Full Pack 12 (Windows, English)









Total purchase amount:

US $269.99









   



 



   

 click to download/view order copy

   



 

ORDER INFORMATION  



   

You purchased a download version of our product. Follow the
instructions below to start using it today:

 

Login into Your Account with the Adobe ID: g...@gnu.org

 

In the My Orders page, locate order AD010031934 with the date March
26, 2018, and expand the order to view the details.

Start your download by clicking on the 'Download' button.

After you have completed the download process, your serial number will
be displayed in the download center.

You can log back into 'My Adobe' in the future to re-download your
product or retrieve your serial number. Please refer to the download
policy for

terms and conditions.

 

For help with downloading and installing your product, visit the

Download and Installation Support center.

     



     

Get started using Adobe tools immediately. We offer a wide range of
additional services to help you get started.

 



Training - From online training to instructor-lead courses, books to
live seminars and events, Adobe helps you get the skills you need.



Online forums - Find peer-to-peer discussions of Adobe products. Log
in today!



   



 

ORDER SERVICES  



 



    Check the

order status page to address any questions about your order.

Have questions? Check out our list of

Frequently Asked Questions.

 





My Adobe - Update your communication preferences or change your email
address.



Thanks again for ordering from the Adobe Store.

Best regards,



The Adobe Store Team
















Re: Thank you!

2013-11-15 Thread Jeff Law

On 11/15/13 18:33, Mark Mitchell wrote:


I'd very much like to thank all who are, have been, or will be
developers and maintainers of GCC.  Of course, I'm particularly
grateful to those who reviewed my patches, fixed the bugs I
introduced, endured my nit-picking reviews of their patches, and so
forth.  But, there are literally hundreds of you -- perhaps thousands
-- who have contributed, and I'd like to thank all of you; your
contributions and your community gave me the opportunity to have a
ton of fun.

And on behalf of the entire GCC community I'd like to thank you.

You played so many roles for GCC through the years.  C++ co-maintainer, 
release manager, steering committee member, global reviewer, project 
leader, etc and excelled at each one.


In particular I'd like to call out your time as release manager.  I 
suspect some of the newer folks aren't aware of how desperately we 
needed someone to step into that role.  I had completely burnt out and 
GCC was floundering with not even a plan for how the next release was 
going to get out the door.


You volunteered for an often thankless job and did far more as a release 
manager than I could ever have envisioned.  You managed to herd a 
diverse group of developers, often with conflicting agendas, &  without 
any true power over how they spent their time.


During your time as release manager you really became a leader for the 
whole project and with your guidance GCC found continued success.



Even though I've been expecting this for a while, I'm still terribly sad 
to see you go.  As I'm sure you know, you're always welcome here in any 
capacity you choose to engage!


Thanks again,

jeff


Thank you!

2013-11-15 Thread Mark Mitchell
Folks --

It's been a long time since I've posted to the GCC mailing list because (as is 
rather obvious) I haven't been directly involved in GCC development for quite 
some time.  As of today, I'm no longer at Mentor Graphics (the company that 
acquired CodeSourcery), so I no longer even have a management role in a company 
involved in GCC development.  And, as I don't have plans to be involved in GCC 
development in the foreseeable future, it seems best to admit that I'm no 
longer a maintainer of GCC.  I've also tendered my resignation to the GCC 
Steering Committee.  David Edelsohn has kindly agreed to make the requisite 
changes to the MAINTAINERS file on my behalf.  

GCC has been an interest of mine for a very long time, beginning with the point 
at which I convinced a previous employer to deploy it as a cross-platform 
compiler solution because we were having so many problems with incompatibility 
between the various proprietary compilers we were using.  Of course, GCC itself 
still had a few bugs left at that point, so I fixed one or two, and, later, 
when I should have been writing papers in graduate school, I implemented some 
C++ template features (with much help from Jason Merrill and others) instead, 
and, eventually became very involved in the development of GCC.  I'll of course 
remain interested in GCC, even if more as an observer than as a participant!

I'd very much like to thank all who are, have been, or will be developers and 
maintainers of GCC.  Of course, I'm particularly grateful to those who reviewed 
my patches, fixed the bugs I introduced, endured my nit-picking reviews of 
their patches, and so forth.  But, there are literally hundreds of you -- 
perhaps thousands -- who have contributed, and I'd like to thank all of you; 
your contributions and your community gave me the opportunity to have a ton of 
fun.

Thank you,

--
Mark Mitchell



Is there any pointers you might have What are the pros and cons I should be looking out for Any info much appreciated Thank you very much John

2009-07-03 Thread mike.power...@gmail.com
Hi,
Is there any pointers you might havewhat are the pros and cons i should be 
looking out for   any info much   appreciatedthank you very muchjohn?
What Gotchas should I be aware of?
Any help appreciated.  Thank you so much.  Regards, Joan


Cannot generate profile data, it's weird, thank you

2008-10-27 Thread Qi齐辉 Hui
Hi folks,

I encountered an weird issue when I using gcc 3.4.6 to build our
project. The profile data (*.gcda files)can not be generated or be
updated when the binary is running as 1 process, only be generated or
be updated with 2 processes when I set the process number as 2 in the
configure file. The configure options are exactly same except the
number of  PROCESS. (-fprofile-generate)

I am so confused. I have exactly same configure files, same code
source, same machine and same environment, And this issue never
happened when I was using gcc 3.2.3.

I was trying to write a demo programme to reproduce it, but I failed,
and I have no ideas what happened? So I write to you for help, please
tell me any possibilities may lead this issue happen?

Thank you very much
rgds
Hui


Re: [graphite] Google Summer of Code 2008 is over - Thank you

2008-08-20 Thread Sebastian Pop
Hi Tobias,

On Wed, Aug 20, 2008 at 4:45 PM, Tobias Grosser
<[EMAIL PROTECTED]> wrote:
> So even if Google Summer of Code has finished. I do not want to say
> "Goodbye", but "Hello" to you.
> I am looking forward to work with you on gcc and graphite!
>

I would like to say a big thank you for your contributions.  It was a
pleasure to work with you during this SOC, and I hope to have your
valuable opinion, remarks and patches for loop optimizations and
parallelization on top of the graphite infrastructure.

Sebastian


[graphite] Google Summer of Code 2008 is over - Thank you

2008-08-20 Thread Tobias Grosser
Hi gcc community, hi graphities,

since Monday Google Summer of Code 2008 is over and I would like to
write a little bit about my SOC project.

First of all I would like to thank Sebastian for being my mentor. It was
really fun to work with you. I never felt alone and always got great
mail or phone response, if I was not sure where to go. And also thanks
to all the other gcc and graphite people, that contributed to graphite
and helped me working on my GSoC project. I got many valuable mails and
bug reports helping me improving my code.

What I really liked was the good integration in the graphite team, so
that from the first days I felt like home. I got all support I needed
and our weekly (except exceptions) phone conferences helped me to get to
know the team better. Now I know some of you by hearing your
voice, but it would be even better to see you once in real live!

I also would like to thank Laurent for the CompileFarm account. A very
useful service for gcc development.

In the last weeks I realized a little problem in my graphite work.
As I worked so well with the graphite folks, I just completely forgot to
use the gcc mailing lists and to get in touch with the countless gcc
developers. So I apologize for this and will try to change this now.

As a starter I would like to inform you, what I have done during the
last 4 months:

What I wanted to do:


[…]

At the moment the general shape of the GRAPHITE framework is quite clear
and people have started to work on different areas. While they reached
new areas of development, it became quite clear, that the GRAPHITE
frontend, the translation from GIMPLE to GRAPHITE has some serious
drawbacks, which stop people to continue their development fast and
efficiently.

During Summer of Code I would like to solve these problems and build a
solid basis for further graphite development.

[…]

More on my proposal at:
http://students.fim.uni-passau.de/~grosser/gcc_soc/

What is done:
=

 1. SCoP detection
 -
We scan the CFG to detect all parts, that we can
transform to the polyhedral representation (GRAPHITE). 

  * This pass works and is verified by the graphite and
polyhedron test suites.
  * We detect conditions containing (<=, <, >, >=), perfect
loop nests with single exit, and allow parameters in
loop borders and conditons.

 2. GIMPLE => GRAPHITE
 -

Now the control flow of the detected SCoPs is translated to the
polyhedral representation. This means loop borders and
conditions are inserted into a matrix, that tells us for which
values of the loop indeces the bbs are executed. 

  * Works for all detected SCoPs

 3. Cloog Output
 ---
Cloog is the library we use to regenerate the CFG. We insert the
polyhedral model and get an ast, describing the loop structure
after applied optimizations. Cloog is also able to optimize in
control structures (e.g. move conditions out of loops)  so even
without optimizations passes we get optimizations. 

  * Works for all detected SCoPs

 4. Loop blocking 
 

  * I wrote a first experimental pass, to show how graphite
transformations work.

So GRAPHITE has now a front end, that is able to detect most of the
common loop nests and get them into the graphite representation. In
Polyhedron e.g. we detect already 411 SCoPs with 536 loops and 1303 bbs.
These are 15% of all loops (3587).

And there is many space for improvements.

What is left to be done:


 1. SCoP detection 
 -
  * Conditional statements containing “||” or “&&”.
  * Switch statements.
  * Loops with multiple exits.
  * Iterative optimization to maximize SCoP size.

 2. GIMPLE => GRAPHITE
 -
  * Conditional statements containing “||” or “&&”.
  * Switch statements.
  * Loops with multiple exits.
  * Allow scev parameter detection in SCoPs, that are not
surrounded by a loop.

 3. Graphite middle end
 --
Here we reach hardly touched ground, where a large number of
optimizations are possible. For example:

  * Dependency detection
  * Loop splitting
  * Loop fusing
  * …
  * Automatic parallization

I will keep on working on graphite, the next weeks on the import and
after that heading to some of the open tasks.

So even if Google Summer of Code has finished. I do not want to say
“Goodbye”, but “Hello” to you.
I am looking forward to work with you on gcc and graphite!

See you

Tobi