Closed Bug 425215 Opened 18 years ago Closed 13 years ago

Need a strategy for Dehydra GCC versions

Categories

(Developer Infrastructure :: Source Code Analysis, defect)

Product:
Developer Infrastructure
Component:
Source Code Analysis
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: stanshebs, Unassigned)

Details

Since the Dehydra plugin hooks into various bits of GCC internals, we are subject to the vagaries of constant change in GCC versions. For instance, on Mac OS X we will likely be using a modified 4.2, while on Linux, 4.3 and 4.4 have some differences in tree handling. We need to decide a) whether to support multiple plugins, or lash down supported GCC versions, and b) whether to use the plugin to establish a consistent API to JS, or allow it to change from time to time.
A summary of discussion in IRC: we could either put Apple GCC 4.2 Preview source in mercurial with patches applied or we could host the tarball of said source to not depend on Apple there and put the patches specific to it on a branch of the repository where Linux patches are.
Dehydra and treehydra are no longer maintained by Mozilla.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: Core → Firefox Build System
Product: Firefox Build System → Developer Infrastructure
You need to log in before you can comment on or make changes to this bug.