<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Hi, Will we accept add the other <span style="color:rgb(32,31,30); font-size:14.6667px; background-color:rgb(255,255,255); display:inline!important">
architectures</span>? A example is Loongarch(Its from China). Will we expectation it is fully public?</div>
<div class="elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div id="appendonsend"></div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Development <development-bounces@qt-project.org> on behalf of Alex Blasche <alexander.blasche@qt.io><br>
<b>Sent:</b> Thursday, August 11, 2022 16:56<br>
<b>To:</b> development@qt-project.org <development@qt-project.org><br>
<b>Subject:</b> Re: [Development] Proposing to add (CPU) architecture maintainers</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">> -----Original Message-----<br>
> From: Development <development-bounces@qt-project.org> On Behalf Of<br>
> Thiago Macieira<br>
> Like I said in my email, we don't have the resources or knowledge to fix<br>
> architectural-specific issues in those platforms, much less apply performance<br>
> improvements. But we will accept patches in case we break anything.<br>
<br>
Keeping the above in mind I would like to bring the thread back to <br>
<a href="https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugreports.qt.io%2Fbrowse%2FQTBUG-103010&amp;data=05%7C01%7C%7Cafc9f20096314d77e25708da7b77ad82%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637958051196070906%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=jTdX7H3q%2B%2B0CWHRdHtXrNqQyfLEvJkK89OgTcl1TtLE%3D&amp;reserved=0" data-auth="NotApplicable">https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugreports.qt.io%2Fbrowse%2FQTBUG-103010&amp;data=05%7C01%7C%7Cafc9f20096314d77e25708da7b77ad82%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637958051196070906%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=jTdX7H3q%2B%2B0CWHRdHtXrNqQyfLEvJkK89OgTcl1TtLE%3D&amp;reserved=0</a><br>
<br>
Currently POWER, MIPS, RISC-V and SPARC are open. Since this is an optimization task, I would argue that we close the subtasks for each of the mentioned platforms as Won't Do. Any objections?<br>
<br>
And yes, we'll happily accept patches as outlined by Thiago.<br>
<br>
--<br>
Alex<br>
<br>
_______________________________________________<br>
Development mailing list<br>
Development@qt-project.org<br>
<a href="https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.qt-project.org%2Flistinfo%2Fdevelopment&amp;data=05%7C01%7C%7Cafc9f20096314d77e25708da7b77ad82%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637958051196070906%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=PLSBsyeBhyBqclZX8CK2yMEh18fsXzCbuyGV64hmuOo%3D&amp;reserved=0" data-auth="NotApplicable">https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.qt-project.org%2Flistinfo%2Fdevelopment&amp;data=05%7C01%7C%7Cafc9f20096314d77e25708da7b77ad82%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637958051196070906%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=PLSBsyeBhyBqclZX8CK2yMEh18fsXzCbuyGV64hmuOo%3D&amp;reserved=0</a><br>
</div>
</span></font></div>
</body>
</html>