This forum is now closed.
Also note this Birds of a Feather session at Supercomputing 2012:
Tuesday, Nov 13th, 5:30 - 7:00pm [Room 355-A]
Birds of a Feather: “OpenMP: Next Release and Beyond” – Barbara M. Chapman, Bronis R. de Supinski, Matthijs van Waveren
We will present and release a comment draft of the next specification version, which includes several significant enhancements, and we will discuss plans for the continued evolution of OpenMP. A lively panel discussion will critique the draft. We will solicit audience opinions on what features are most needed for future specifications. http://sc12.supercomputing.org/schedule ... vid=bof112.
Is there a (quick) way to see the chages wrt version 3.1? I've seen the text
but I'm not able to relate those to the actual text (I don't know the so called "change tickets").This is a public draft release candidate, based on version 3.1, incorporating
the following internal change tickets:
71, 77, 90, 88, 111, 125, 126, 136, 137, 138, 144, 146, 147,
148, 149, 150, 151, 152, 154, 155, 156, 157, 164, 166, 168,
169, 170, 172, 173, 174, 175, 176
Thanks in advance,
That said, unfortunately at this time, I know of no easy way for an individual outside the committee to easily see the changes. If you have a suggestion as to how you would like to see the information about the changes, I am sure that the committee would be happy to consider it.
Right, I forgot to see Appendix F, thanks for the remainder.In theory, Appendix F should contain a summary of the changes that have been made for each release.
Hmmm... maybe the "change bars" are very good to see specific changes beyond those explained/referred to in Appendix F.If you have a suggestion as to how you would like to see the information about the changes, I am sure that the committee would be happy to consider it.
I would rather like to see a more detailed section F.1 indicating which sections in the document are new and updated for each new feature. The list of "tickets" is for internal accounting but a summary could be provided. We'll look into this for RC2 and the final release.