Re: GCC 8.2 Status Report (2018-07-19), branch frozen for release
On 24/07/18 17:30, Richard Biener wrote: > On July 24, 2018 5:50:33 PM GMT+02:00, Ramana Radhakrishnan > wrote: >> On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener >> wrote: >>> >>> Status >>> == >>> >>> The GCC 8 branch is frozen for preparation of the GCC 8.2 release. >>> All changes to the branch now require release manager approval. >>> >>> >>> Previous Report >>> === >>> >>> https://gcc.gnu.org/ml/gcc/2018-07/msg00194.html >> >> Is there any chance we can get some of the spectrev1 mitigation >> patches reviewed and into 8.2 . > > It's now too late for that and it has to wait for 8.2. Why? It was waiting on YOU for a review and was posted before you announced the freeze. R. > >> It would be quite useful to get these into a release as I see that the >> reviews are kinda petering out and there hasn't been any objection to >> the approach. > > It's not that people only use release tarballs. > > Richard. >> >> >> regards >> Ramana >
Re: GCC 8.2 Status Report (2018-07-19), branch frozen for release
On Wed, 25 Jul 2018, Richard Earnshaw (lists) wrote: > On 24/07/18 17:30, Richard Biener wrote: > > On July 24, 2018 5:50:33 PM GMT+02:00, Ramana Radhakrishnan > > wrote: > >> On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener > >> wrote: > >>> > >>> Status > >>> == > >>> > >>> The GCC 8 branch is frozen for preparation of the GCC 8.2 release. > >>> All changes to the branch now require release manager approval. > >>> > >>> > >>> Previous Report > >>> === > >>> > >>> https://gcc.gnu.org/ml/gcc/2018-07/msg00194.html > >> > >> Is there any chance we can get some of the spectrev1 mitigation > >> patches reviewed and into 8.2 . > > > > It's now too late for that and it has to wait for 8.2. > > Why? It was waiting on YOU for a review and was posted before you > announced the freeze. There's nothing like posting before freeze gives you extra time like we do when transitioning to stage3. You are requesting a feature backport anyway. Anyway, you got a review from ME that showed the series isn't ready, esp. for going into a stable code-base last minute before a release. But I assume "YOU" addressed all volunteer GCC reviewers. Richard.
r227907 and AIX 5.[23]
r227907 had the following change:
Index: aix61.h
===
--- aix61.h (revision 227906)
+++ aix61.h (revision 227907)
@@ -167,7 +167,7 @@
%{!maix64:\
%{pthread:%{pg:gcrt0_r%O%s}%{!pg:%{p:mcrt0_r%O%s}%{!p:crt0_r%O%s}}}\
%{!pthread:%{pg:gcrt0%O%s}%{!pg:%{p:mcrt0%O%s}%{!p:crt0%O%s}\
- %{shared:crtcxa_s%O%s;:crtcxa%O%s}"
+ %{shared:crtcxa_s%O%s;:crtcxa%O%s} crtdbase%O%s"
/* AIX V5 typedefs ptrdiff_t as "long" while earlier releases used "int". */
In trying to build gcc-8.1.0 on AIX 5.3 (cf. PR86553), I looked at how
libgcc_s.a was built and, on AIX 6 and 7, crtdbase was linked in,
providing __gcc_unwind_dbase (and crtcxa_s for __dso_handle). However,
on AIX 5.3, this file is never included because
gcc/config/rs6000/aix53.h has:
#undef STARTFILE_SPEC
#define STARTFILE_SPEC "%{!shared:\
%{maix64:%{pg:gcrt0_64%O%s}%{!pg:%{p:mcrt0_64%O%s}%{!p:crt0_64%O%s}}}\
%{!maix64:\
%{pthread:%{pg:gcrt0_r%O%s}%{!pg:%{p:mcrt0_r%O%s}%{!p:crt0_r%O%s}}}\
%{!pthread:%{pg:gcrt0%O%s}%{!pg:%{p:mcrt0%O%s}%{!p:crt0%O%s}"
A patch similar to the above must also be made to aix53.h for 8.1.0 to
build successfully on AIX 5.3. At the moment, GCC 5+ doesn't build on
AIX 5.3 because of the above.
--
albert chin (ch...@thewrittenword.com)
Re: r227907 and AIX 5.[23]
AIX 5.3 no longer is under supported or maintained.
- David
On Wed, Jul 25, 2018 at 1:13 PM Albert Chin
wrote:
>
> r227907 had the following change:
> Index: aix61.h
> ===
> --- aix61.h (revision 227906)
> +++ aix61.h (revision 227907)
> @@ -167,7 +167,7 @@
> %{!maix64:\
> %{pthread:%{pg:gcrt0_r%O%s}%{!pg:%{p:mcrt0_r%O%s}%{!p:crt0_r%O%s}}}\
> %{!pthread:%{pg:gcrt0%O%s}%{!pg:%{p:mcrt0%O%s}%{!p:crt0%O%s}\
> - %{shared:crtcxa_s%O%s;:crtcxa%O%s}"
> + %{shared:crtcxa_s%O%s;:crtcxa%O%s} crtdbase%O%s"
>
> /* AIX V5 typedefs ptrdiff_t as "long" while earlier releases used "int". */
>
> In trying to build gcc-8.1.0 on AIX 5.3 (cf. PR86553), I looked at how
> libgcc_s.a was built and, on AIX 6 and 7, crtdbase was linked in,
> providing __gcc_unwind_dbase (and crtcxa_s for __dso_handle). However,
> on AIX 5.3, this file is never included because
> gcc/config/rs6000/aix53.h has:
> #undef STARTFILE_SPEC
> #define STARTFILE_SPEC "%{!shared:\
> %{maix64:%{pg:gcrt0_64%O%s}%{!pg:%{p:mcrt0_64%O%s}%{!p:crt0_64%O%s}}}\
> %{!maix64:\
>%{pthread:%{pg:gcrt0_r%O%s}%{!pg:%{p:mcrt0_r%O%s}%{!p:crt0_r%O%s}}}\
>%{!pthread:%{pg:gcrt0%O%s}%{!pg:%{p:mcrt0%O%s}%{!p:crt0%O%s}"
>
> A patch similar to the above must also be made to aix53.h for 8.1.0 to
> build successfully on AIX 5.3. At the moment, GCC 5+ doesn't build on
> AIX 5.3 because of the above.
>
> --
> albert chin (ch...@thewrittenword.com)
Re: r227907 and AIX 5.[23]
On Wed, Jul 25, 2018 at 01:15:44PM -0400, David Edelsohn wrote: > AIX 5.3 no longer is under supported or maintained. Ok. Well, we can now build 8.1 with this change so we'll update the PR and leave it to someone else to decide if the patch should be merged. -- albert chin (ch...@thewrittenword.com)
You're my victim
Hi, victim. I writе yоu beсause I put a mаlwаrе on the wеb рagе with porn which yоu hаvе visited. My virus grаbbеd all your рersonal info аnd turned on your cаmеra which cарturеd thе prосеss оf your оnаnism. Just aftеr thаt the soft saved your соntaсt list. I will delеtе the соmpromising vidеo аnd infо if you pаy me 999 EURO in bitcоin. This is addrеss fоr рaymеnt : 1G8TaC3eD6CAaKVFi7DoXbEhk7UZwSK2BD I give you 30 hours after you oреn my messаgе for mаking thе trаnsaсtiоn. As soon аs you rеad the messаgе I'll sеe it right аwаy. It is not neсessary tо tеll me thаt you hаvе sent monеy to me. This addrеss is connected to yоu, my systеm will dеletе everything automaticаlly аftеr transfer confirmаtion. If you need 48 h just reрly оn this lеttеr with +. You cаn visit thе роliсе statiоn but nоbоdy саn helр you. If yоu try to deсеivе mе , I'll see it right awаy ! I dont live in your сountry. Sо they cаn not trаck my lоcatiоn еven for 9 mоnths. Goodbye. Dont forgеt аbout the shаme and to ignore, Yоur life саn bе ruinеd.
Re: r227907 and AIX 5.[23]
On Wed, 25 Jul 2018, David Edelsohn wrote: AIX 5.3 no longer is under supported or maintained. If gcc-5+ fails to build on AIX 5.3 and patches to make it compile are not welcome, maybe some cleanup removing aix43.h, aix5*.h and whatever configure bits could help clarify things? Only when someone has the time, of course. -- Marc Glisse
gcc-6-20180725 is now available
Snapshot gcc-6-20180725 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/6-20180725/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6-branch revision 262983 You'll find: gcc-6-20180725.tar.xzComplete GCC SHA256=4247ead7368da9d12ce10cd15524010540c4d9791d982c766719196b040f8930 SHA1=60fea35e0c7d61272b887c6e3eec5223971f5ade Diffs from 6-20180718 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-6 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
[CFP] 2018 2nd Int. Conf. on Research & Innovation in Comp. Eng. & Comp. Sciences on 18-20 September 2018 in Melaka, Malaysia. Submission Deadline 31st July 2018!!!
We apologize if you receive multiple copies of this message.Please disseminate this CFP to your colleagues & contacts. 2018 2nd International Conference on Research and Innovation in Computer Engineering and Computer Sciences (RICCES2018) **https://ricces.maltesas.my/** 18 - 20 September | Melaka SUBMISSION DEADLINE :- 31st July 2018!!! Submit :- https://edas.info/N24813 All accepted 2-pages extended abstracts or full-length paper will be published in MALTESAS Proceedings with e-ISBN on our MALTESAS Explore, which will be indexed in Google Scholar. In addition, the proceedings will also be submitted to SCOPUS for indexing consideration. * This international level conference its aim to be more specific in the development and cutting-edge papers related to Research and Innovation in Computer Engineering and Computer Sciences. The main goal of the RICCES 2018 is to provide an opportunity for academicians and professionals from various Computer Engineering and Computer Sciences related fields from all over the world to come together and learn from each other. An additional goal of the conference is to provide a place for academicians and professionals with cross-disciplinary interests related to Computer Engineering and Computer Sciences to meet and interact with members inside and outside their own disciplines. RICCES 2018 aims to be a premier venue for researchers and industry practitioners to share their new ideas, original research results and practical development experiences in Computer Engineering and Computer Sciences. CONFERENCE TRACK: TRACKS 1 : ELECTRONICS AND COMPUTER ENGINEERING TRACK 2 : COMPUTER SCIENCE AND INFORMATION TECHNOLOGY See You in Melaka, Malaysia Click here to unsubscribe from future mailings: http://list14.ebu.com/proc.php?nl=4&c=297&m=336&s=959f5473b16cc30ebe4a58c5db2a931d&act=unsub
