[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] Issue with ETFw and UPC
|
I second this. The fix is pretty easy (just add checks for those other strings) and shouldn't have any impact on other plugins.
=Wyatt
On Mon, Jun 7, 2010 at 10:27 AM, Max Billingsley III
<billingsley@xxxxxxxxxxx> wrote:
This is a message regarding an ETFw issue, intended mainly for Wyatt.
There is an issue in the ETFw that is preventing profiling runs (in particular using PPW) of UPC applications from working properly. I am using the Berkeley UPC toolchain (part of CDT), and the (instrumented) build step hangs at the "Instrumenting/Building" step.
After investigating the problem, I've found that the ETFw is assuming a certain naming convention for the tool ID which does not in fact apply. Here are the relevant lines in BuilderTool.java in the org.eclipse.ptp.etfw.internal package, starting at 449:
if (toolid.indexOf(".upc.") >= 0) //$NON-NLS-1$
{
numChanges += modifyCommand(tools[i], getToolCommand(tool.getUPCCompiler(),
configuration), allargs, tool.replaceCompiler);
}
However the toolid for Berkeley UPC is the following:
org.eclipse.cdt.managedbuild.tool.bupc.compiler.exe.debug.####
(where #### is a number corresponding to an individual instance of the tool, from what I can tell).
The same issue would apply for the XLUPC toolchain, as its toolid would be of this form:
cdt.managedbuild.tool.compiler.xlupc.exe.debug
Because this issue prevents the ETFw from working properly with UPC, I think it's important to get a simple fix committed in time for Helios.
Thanks,
-Max
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
